[DERBY-4440] Intermittent Java deadlock when running LobStreamsTest with insane jars

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.6.1.0
• Component/s: Store
• Environment: Dual core CPU at 3.2 GHz, OpenSolaris, Java HotSpot(TM) Client VM (14.1-b02 mixed mode)
• Assignee: Unassigned
• Reporter: Kristian Waagan
• Created: 10/Nov/09 12:55
• Updated: 23/Mar/10 09:30
• Resolved: 25/Feb/10 09:58

Description

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.

Issue Links

• duplicates: DERBY-3844 ASSERT failure in BasePage.unlatch() when running LobStreamsTest