Re: Blocked trying to get lock: org.apache.log4j.spi.RootLogger

2015-08-06 Thread Aakash Pravin Lodha
652" seconds working on the request "weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl@58887aee", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace: Thread-3471 "[STUCK] ExecuteThread: '16' for queue: 'web

Re: Blocked trying to get lock: org.apache.log4j.spi.RootLogger

2009-09-25 Thread Simon B
Hi Dave, I'm running into a similar problem, Regards what you did to remidy the problem, i.e. increase the quantity of file descriptors available to the process, am I right in thinking that the process was using > 1024 open file descriptors? Its just when I take a look at our server using the

Re: Blocked trying to get lock: org.apache.log4j.spi.RootLogger

2009-07-17 Thread laredotornado
Here is my contribution to the good of humanity. The below problem went away when we increased the number of file descriptors available to our WebLogic managic server process from 1024 to 65K. - Dave laredotornado wrote: > > Hi, We are using WebLogic 9.2.2 with Java 1.5. The application is w

Blocked trying to get lock: org.apache.log4j.spi.RootLogger

2009-07-01 Thread laredotornado
Hi, We are using WebLogic 9.2.2 with Java 1.5. The application is written using Struts 1.3 and log4j 1.2.15. We found a number of errors that looked like below in our managed server's .out file. Any ideas what might be a cause or how to troubleshoot further? Our sys admin sadly did not preserv