Netty causing all log4j logging to duplicate

["이희승 (Trustin Lee)"]

That's very weird.

Did you set the InternalLoggerFactory to Log4JLoggerFactory to switch
from j.u.logging to Log4J?

    InternalLoggerFactory.setDefaultFactory(new Log4JLoggerFactory());

If you did not, please do so before any other Netty classes are loaded.
 I'm not sure it will fix the problem though.  Perhaps you've set this
already..

HTH,
Trustin

On 07/08/2010 12:53 AM, jasons2645 wrote:
> 
> Unfortunately, the issue's not a simple matter of logging the event twice. 
> The issue is that once the connection failure occurs, ALL log4j loggers have
> duplicate logging until the JVM terminates.  For example,
> 
>> INFO 2010-07-01 10:36:22,188 C:client.gui T:AWT-EventQueue-0 | Sasm
>> terminating the application.
>> 32953 [AWT-EventQueue-0] INFO com.pillardata.client.gui  - Sasm
>> terminating
>> the application. 
> 
> The above log statements are duplicated (and even more strangely, with a
> different pattern string).  If we don't get the connection attempt failure,
> no duplicate logging like this ever occurs in the lifetime of the app.  If
> however we do log this, duplicate logging will occur henceforth across all
> loggers.
> 
> It's almost as if Netty is appending loggers to the configuration, but I
> don't see anything like that...  This behavior has been baffling to say the
> least...

-- 
what we call human nature in actuality is human habit
http://gleamynode.net/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 293 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/netty-users/attachments/20100712/f07df88f/attachment.bin