Issue with locking in MsgRepository implementation (#700)

Closed

Activities

Andrzej Wójcik (Tigase) opened 8 years ago

Due Date
2016-08-11

Issue was reported in message#6765 with following stacktrace:

2016-08-05 08:46:16.760 [expired-processor] ThreadExceptionHandler.uncaughtException() SEVERE: Uncaught thread: "expired-processor" exception
java.lang.IllegalMonitorStateException
at java.util.concurrent.locks.ReentrantLock$Sync.tryRelease(Unknown Source)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.release(Unknown Source)
at java.util.concurrent.locks.AbstractQueuedSynchronizer.fullyRelease(Unknown Source)
at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Unknown Source)
at tigase.server.amp.db.MsgRepository$MsgRepositoryMDBean.getMessageExpired(MsgRepository.java:295)
at tigase.server.amp.action.Store$1.run(Store.java:220)

Andrzej Wójcik (Tigase) commented 8 years ago

Fixed issue related to locks and conditions which may manifest when expired message is found in offline store.

Type	Bug
Priority	Normal
Assignee	Andrzej Wójcik (Tigase)
RedmineID	4447
Version	tigase-server-8.0.0
Spent time	2h 30m

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#700