Timed Resource Pool caused Confluence to crash

XMLWordPrintable

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: High
    • 2.0
    • Affects Version/s: None
    • Component/s: None
    • None

      CAC went down with the errors attached to this issue.

      Scott wrote:

      Here seems to be the offending statement (well, apart from the Webwork one):

      "Thread-1" daemon prio=1 tid=0x8dbace98 nid=0x18d waiting for monitor entry [8d994000..8d99486c]
      at java.util.LinkedList.clone(LinkedList.java:602)
      at com.mchange.v2.resourcepool.BasicResourcePool.cloneOfUnused(BasicResourcePool.java:1044)
      at com.mchange.v2.resourcepool.BasicResourcePool.cullExpiredAndUnused(BasicResourcePool.java:934)
      at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:31)
      at com.mchange.v2.resourcepool.BasicResourcePool$CullTask.run(BasicResourcePool.java:1138)

      • locked <0x931f2c20> (a com.mchange.v2.resourcepool.BasicResourcePool)
        at java.util.TimerThread.mainLoop(Timer.java:432)
        at java.util.TimerThread.run(Timer.java:382)

      Seems that the resource pool has a timed tast that does something. However, it seems like that must take quite a long time?

        1. sysout-2005-07-25_052834.log
          800 kB

              Assignee:
              Unassigned
              Reporter:
              jens
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: