https://issues.apache.org/bugzilla/show_bug.cgi?id=41214
--- Comment #33 from Adilson Dias <[email protected]> 2011-02-02 19:05:49 EST --- Replaced log4j with logback and everything works fine. No deadlock. Cheers, Adilson Dias (In reply to comment #32) > Log4J version 1.2.16: > Deadlock: > [2/1/11 15:22:44:977 EST] 00000005 TimeoutManage I WTRN0124I: When the > timeout occurred the thread with which the transaction is, or was most > recently, associated was Thread[WMQJCAResourceAdapter : 3,5,main]. The stack > trace of this thread when the timeout occurred was: > java.io.UnixFileSystem.getBooleanAttributes0(Native Method) > java.io.UnixFileSystem.getBooleanAttributes(UnixFileSystem.java:240) > java.io.File.exists(File.java:733) > > org.apache.log4j.RollingFileAppender.rollOver(RollingFileAppender.java:151) > > org.apache.log4j.RollingFileAppender.subAppend(RollingFileAppender.java:280) > org.apache.log4j.WriterAppender.append(WriterAppender.java:162) > org.apache.log4j.AppenderSkeleton.doAppend(AppenderSkeleton.java:251) > > org.apache.log4j.helpers.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:66) > org.apache.log4j.Category.callAppenders(Category.java:206) > org.apache.log4j.Category.forcedLog(Category.java:391) > org.apache.log4j.Category.debug(Category.java:260) > Component1Impl.logDebug(Component1Impl.java:140) > > Multiple-threaded application, installed on WebSphere Application Server v7, > picking messages from a JMS Queue on WebSphere MQ v7. At the time 10 > connections where opened retrieving messages from the queue and writing to a > log file. > Application stopped while Log4J tried to rollover the log file, timing out > the > session. > > So, how can we fix this? > Thanks! > Adilson Dias -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
