Netty causing all log4j logging to duplicate

[jasons2645]

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...
-- 
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Netty-causing-all-log4j-logging-to-duplicate-tp5244186p5265923.html
Sent from the Netty User Group mailing list archive at Nabble.com.