Thanks for merging in log4j.
Its a great facility.
I have a question about some observed behavior.
Using a fresh CVS checkout and build from this morning...
When I disable ConsoleLogger and FileLogger in jboss.conf
(by commenting them out) and enable the log4j mbean, I get
duplicate output on the console. I've annotated the pattern
string in the log4j properties enough to be able to
distinguish output which is originating from log4j VS output
which is originating somewhere else. One copy of the output
is coming from log4j the other is not.
I just wanted to ask if this is the expected behavior or not
to know if I should dig in and figure out why other
(non-log4j) output is appearing on the console. I was under
the impression that commenting out the ConsoleLogger would
get rid of the original output.
Thanks.
Scott M Stark wrote:
>
> I integrated Fulco Muriglio's log4j based mbean into the org.jboss.logging
> package and updated the jboss.conf to make it simple to switch to this as
> the logging service. It probably should be made the default logging service
> in the future as the log4j framework is a superset of the JBoss logging. There
> is nothing that prevents the use of the org.jboss.logging.Log4jService and
> org.jboss.logging.Log4jServiceMBean classes in any previous version of
> JBoss so you could grab the source and integrate the mbean into previous
> versions. The comments in the latest jboss.conf along with the
> conf/default/log4.properties should be all you need to switch to Log4jService
> for 2.1+ as the 1.0.4 log4j.jar is already in the distribution.
>
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
