[DERBY-1040] Run store locking tests with network server and investigate locking behaviour

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 10.2.1.6
• Component/s: Network Client, Network Server
• Labels: derby_triage10_8
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 23/Feb/06 23:07
• Updated: 06/Oct/14 21:12

Description

The store locking tests should be run with network server, locking behaviour investigated, and a perhaps a proposal made for testing locking with network server. For network server, the pre-fetching of data causes diffs in the tests and I am not sure if this is expected or not. I noticed for example such diffs in updatelocks.sql and readlocks.sql.

Below is the list of locking tests I see in store. Feel free to take one or two and file a subtask.

EscalateLock.sql
RowLockBasic.sql
RowLockIso.sql
TableLockBasic.sql
TableLockBasic.subsql
lockTableVti.sql
readBtreeCursorLocks.subsql
readBtreeSetLocks.subsql
readCursorLocks.subsql
readSetLocks.subsql
readlocks.sql
updateBtreeCursorLocks.subsql
updateBtreeHoldCursorLocksJDBC30.subsql
updateBtreeSetLocks.subsql
updatecursorlocks.subsql
updateholdcursorlocksJDBC30.subsql
updatelocks.sql
updatelocksJDBC30.sql
updatesetlocks.subsql
RowLockIso.sql
rlliso1multi.sql
rlliso1multi.subsql
rlliso2multi.sql
rlliso3multi.sql

Issue Links

• is related to: DERBY-1342 Run derbyall suite with -Dframework=DerbyNetClient and analyze failures