- status: open --> closed-out-of-date
Under high load we occasionally see the following error
message on JBoss 3.0.4's console.
ERROR: invalid console appender config detected, console
stream is looping
Since this only happens at high load and log message
appear fine the rest of the time, I'm reluctant to believe
we have an invalid config. I'm 95% certain we do not
have more than one console appender.
Looking at the source for JBoss 3.0.7 in
org.jboss.logging.util.CategoryStream.java (the only place
I found this error message), it looks like there is some
suspect code in the write(byte[], int, int) method.
The error message is triggered by inWrite being true.
Setting/reading inWrite is guarded by synchronized
blocks.
I believe that if a Category is marked static in some
class, then multiple threads can enter the write method.
If a thread is in between the two synchronized blocks
when another thread calls write, inWrite will be true
because of threading issues, not config issues, and thus
will display the ERROR.