[DERBY-7044] Derby network server failed to shutdown

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.14.2.0
• Component/s: Network Server
• Urgency: Normal
• Bug behavior facts: Performance, Seen in production
• Assignee: Unassigned
• Reporter: Brett Bergquist
• Created: 03/May/19 10:45
• Updated: 03/May/19 10:45

Description

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 Source)

        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)