Project

General

Profile

Bug #4447

Issue with locking in MsgRepository implementation

Added by Andrzej Wójcik IoT 1 CloudTigaseTeam over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
2016-08-05
Due date:
2016-08-12
% Done:

100%

Estimated time:
Database:
n/a
Applicable version:
git/master
Source Code Disclaimer:

Description

Issue was reported in 7.0.4 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)

Associated revisions

Revision 03bc51b5 (diff)
Added by Andrzej Wójcik IoT 1 CloudTigaseTeam over 2 years ago

Bug #4447 - fixed issue with use of locks and conditions

History

#1 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam over 2 years ago

  • Due date set to 2016-08-12
  • Status changed from New to Resolved
  • % Done changed from 0 to 100

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

#2 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam over 2 years ago

  • Description updated (diff)

#3 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF