Menu ▾ ▴

#57 Console handler hangs!!!

open
nobody
None
5
2002-09-17
2002-09-17
No

We had a bug that our container hanged on several occasions.
When we ran it in debug we came to the conclusion that the thread
hung in the console handler.

Thread [JMS Session
Delivery Thread]
(Suspended)
java.io.FileOutputStream.writeBytes(byte[],
int, int) line: not available [native
method]
java.io.FileOutputStream.write(byte[], int, int)
line: 207 [local variables
unavailable]
java.io.BufferedOutputStream.flushBuffer()
line: 67 [local variables
unavailable]
java.io.BufferedOutputStream.flush() line:
125 [local variables
unavailable]
java.io.PrintStream.write(byte[], int, int) line:
219 [local variables
unavailable]
java.io.OutputStreamWriter.flushBuffer()
line: 225 [local variables
unavailable]
java.io.OutputStreamWriter.flush() line: 239
[local variables
unavailable]
java.util.logging.ConsoleHandler(java.util.logging.StreamHandler).flush()
line:
160
java.util.logging.ConsoleHandler.publish(java.util.logging.LogRecord)
line:
56
java.util.logging.Logger.publish(java.util.logging.LogRecord)
line:
279
java.util.logging.Logger.publish(java.util.logging.LogRecord)
line:
283
java.util.logging.Logger.log(java.util.logging.LogRecord)
line:
265
java.util.logging.Logger.logp(java.util.logging.Level,
java.lang.String, java.lang.String, java.lang.String) line:
294
ebitec.framework.Category.debug(java.lang.Object)
line: 57
etc…

Discussion


Log in to post a comment.