Intermittent Java deadlock when running LobStreamsTest with insane jars
-----------------------------------------------------------------------
Key: DERBY-4440
URL: https://issues.apache.org/jira/browse/DERBY-4440
Project: Derby
Issue Type: Bug
Components: Store
Affects Versions: 10.6.0.0
Environment: Dual core CPU at 3.2 GHz, OpenSolaris, Java HotSpot(TM)
Client VM (14.1-b02 mixed mode)
Reporter: Kristian Waagan
Attachments: java-deadlock.txt
The following deadlock was obtained by using jstack when the test
LobStreamsTest hung:
Found one Java-level deadlock:
=============================
"Finalizer":
waiting to lock monitor 0x080f2038 (object 0xceb8ef08, a
org.apache.derby.impl.store.raw.data.StoredPage),
which is held by "main"
"main":
waiting to lock monitor 0x082b5ef8 (object 0xceb98fe8, a
org.apache.derby.impl.store.raw.data.BaseContainerHandle),
which is held by "Finalizer"
The deadlock is highly intermittent. In many cases the test pass, and when it
fails it is mostly with a different symptom than a deadlock (assert error or an
IOException / SQLException).
The problems seem to be triggered by using Clobs, but I don't know if it may be
triggered in other environments as well.
It is likely that DERBY-3844 describes the assert caused by the same underlying
issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
