dao zhang
Added over 2 years ago

2016-08-05 08:46:16.760 [expired-processor] ThreadExceptionHandler.uncaughtException() SEVERE: Uncaught thread: "expired-processor" exception


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(

at tigase.server.amp.action.Store$

Replies (1)

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

Thank you for reporting this issue. I created bug report #4447 in which it will be fixed.

I do not know what 7.0.4 in your topic refers to as this issue may appear only in unstable version 7.2.0-SNAPSHOT which is now in master branch of our Git repository. (Class tigase.server.amp.db.MsgRepository never existed before - it was created in version 7.2.0-SNAPSHOT).