3 Replies Latest reply: Jan 9, 2013 8:03 AM by Kalyan Pasupuleti-Oracle RSS

    weblogic.work.SelfTuningWorkManagerImpl Thread have "STUCK" threads

    Thirunavukkarasu Muthuswamy
      Oracel Weblogic application servers have stuck threads due to this thread "weblogic.work.SelfTuningWorkManagerImpl", the following error message is part of diganostic image logging.img.

      Server: Oracle Weblogic Application Server 11g
      OS: Redhat

      Error Message:

      <web:log-message>[STUCK] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "655" seconds working on the request "weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl@5fe5d29", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
           oracle.jdbc.driver.PhysicalConnection.rollback(PhysicalConnection.java:3916)
           weblogic.jdbc.wrapper.Connection.forcedCleanup(Connection.java:153)
           weblogic.common.resourcepool.ResourcePoolImpl.timeoutInactiveResources(ResourcePoolImpl.java:1953)
           weblogic.common.resourcepool.ResourcePoolImpl.access$1500(ResourcePoolImpl.java:41)
           weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2675)
           weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
           weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:528)
           weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
           weblogic.work.ExecuteThread.run(ExecuteThread.java:176)</web:log-message>

      Please help me in finding out why we are facing stuck threads in this self tuning work manager.