StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow to configure OpenEJB client logging?
text
Body
copied!<p>We are using OpenEJB clients that connect to one OpenEJB server container. The OpenEJB servers are managed by Corosync and Pacemaker for fail-over operation. Whenever an OpenEJB instance fails (caused by network, hardware, JVM or other problems) Corosync+Pacemaker starts another OpenEJB server instance in another machine. The process is relatively fast so that this is not a problem for our use cases.</p> <p>Although OpenEJB provides a native fail-over mechanism, we still chose to manage it with our own mechanism, because that way we can better control the client. Everything is working as expected, except for the client logging that is too verbose. We would like to either turn it off or fine tune it in order to disable connection failure messages, such as this:</p> <blockquote> <p>22/08/2011 14:06:23 org.apache.openejb.client.StickyConnectionStrategy connect AVISO: Failover: Cannot connect to server(s): ejbd://192.168.1.5:4201 Exception: Cannot connect to server 'ejbd://192.168.1.5:4201'. Check that the server is started and that the specified serverURL is correct.. Trying next.</p> </blockquote> <p>I've already tried to decrease the logging level for log4j in the OpenEJB client, but I failed. According to <a href="http://logging.apache.org/log4j/1.2/manual.html" rel="nofollow noreferrer">the log4j documentation</a> and to <a href="https://stackoverflow.com/questions/4176924/how-to-configure-openejb-logging/4280414#4280414">this post</a> it should be a matter of setting the desired level to "error" or "fatal". The question is, what is the category name?</p> <p>I've already tried:</p> <ul> <li>p.put("log4j.category.OpenEJB.client", "error");</li> <li>p.put("log4j.category.OpenEJB", "error");</li> </ul> <p>But nothing has changed. So, what property do I need to use to turn those WARN messages off?</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload