db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brett Bergquist (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DERBY-7044) Derby network server failed to shutdown
Date Fri, 03 May 2019 10:46:00 GMT
Brett Bergquist created DERBY-7044:

             Summary: Derby network server failed to shutdown
                 Key: DERBY-7044
                 URL: https://issues.apache.org/jira/browse/DERBY-7044
             Project: Derby
          Issue Type: Bug
          Components: Network Server
    Affects Versions:
            Reporter: Brett Bergquist
         Attachments: derby-0.log, stacktrace.txt

Derby network server failed to shutdown.  It was hung up and had to be killed manually.

See the stack trace and also the derby-0.log attached. 

It looks like it got stuck when a XA transaction was to be rolled back because the shutdown
was done while one was in progress.  It was waiting on a condition:
"main" #1 prio=5 os_prio=64 tid=0x000000000041f800 nid=0x2 waiting on condition [0xfffffd7ffd48d000]

   java.lang.Thread.State: WAITING (parking)

        at sun.misc.Unsafe.park(Native Method)

        - parking to wait for  <0xfffffd7fa4397110> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)

        at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)

        at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976)

        at org.apache.derby.impl.services.cache.CacheEntry.waitUntilIdentityIsSet(Unknown

        at org.apache.derby.impl.services.cache.ConcurrentCache.getEntry(Unknown Source)

        at org.apache.derby.impl.services.cache.ConcurrentCache.find(Unknown Source)

        at org.apache.derby.impl.store.raw.data.CachedPage.writePage(Unknown Source)

This message was sent by Atlassian JIRA

View raw message