[#SES-1062] IllegalArgumentException: timeout value is negative

Issue Details [XML]

Key:	SES-1062
Type:	Bug
Status:	Resolved
Resolution:	Fixed
Priority:	Major
Assignee:	James Leigh
Reporter:	James Leigh
Votes:	0
Watchers:	0

Operations

If you were logged in you would be able to see more operations.

Sesame

IllegalArgumentException: timeout value is negative

Created: 18/Jul/12 06:52 PM Updated: 18/Jul/12 07:36 PM

Component/s:

Memory Sail

Affects Version/s:

2.6.7, 2.6.8

Fix Version/s:

2.6.9

Description

We also see some cases of uncaught IllegalArgumentExceptions in the MemoryStore sync thread:

As per http://sourceforge.net/mailarchive/message.php?msg_id=29558521

ERROR 11:13:39,490 [Thread-5] STDERR Exception in thread "MemoryStore snapshot cleanup"
ERROR 11:13:39,490 [Thread-5] STDERR java.lang.IllegalArgumentException: timeout value is negative
ERROR 11:13:39,490 [Thread-5] STDERR at java.lang.Object.wait(Native Method)
ERROR 11:13:39,491 [Thread-5] STDERR at info.aduna.concurrent.locks.LockManager.waitForActiveLocks(LockManager.java:126)
ERROR 11:13:39,491 [Thread-5] STDERR at info.aduna.concurrent.locks.AbstractReadWriteLockManager.waitForActiveReaders(AbstractReadWriteLockManager.java:95)
ERROR 11:13:39,491 [Thread-5] STDERR at info.aduna.concurrent.locks.ReadPrefReadWriteLockManager.getWriteLock(ReadPrefReadWriteLockManager.java:113)
ERROR 11:13:39,491 [Thread-5] STDERR at org.openrdf.sail.memory.MemoryStore.cleanSnapshots(MemoryStore.java:916)
ERROR 11:13:39,491 [Thread-5] STDERR at org.openrdf.sail.memory.MemoryStore$2.run(MemoryStore.java:969)
ERROR 11:13:39,491 [Thread-5] STDERR at java.lang.Thread.run(Thread.java:662)

All

Comments

Change History

Sort Order:

[ Permlink ]

Comment by James Leigh [18/Jul/12 07:36 PM]

Revision 11899 checks to ensure the timeout value does not go over the max int value and increases the initial timeout from 1 second to 10 seconds before trying to recover from a potential dead lock.