[ openjms-Bugs-768543 ] Deadlock btw LeaseManager and DestinationManager.collectGarb
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.comp.java.openjms.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #768543, was opened at 2003-07-10 01:41 Message generated for change (Settings changed) made by tanderson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474136&aid=768543&group_id=54559 Category: server Group: v0.7.5 Status: Open Resolution: None Priority: 5 Submitted By: David Magro Martin (dmagrom) >Assigned to: Tim Anderson (tanderson) Summary: Deadlock btw LeaseManager and DestinationManager.collectGarb Initial Comment: We think we have discovered a deadlock problem.... We have 5 clients connected to our openjms server. At the moment we are not using any MessagerListeners in the consumer threads, but rather doing continous polling (receiveNoWait) with a 5ms interval. Since we have no listeners and do no receive, there are intervals with no consumer threads attached to the corresponding destination cache. So, every second (default setting) the cache gets garbaged-collected, but at the same time there are expired messages in the cache and the lease manager tries to remove them. This produces a deadlock as can be seen in the stack trace (attached file). All our messages are persistent (mysql backend) and some of them have a TTL. Thank you very much. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=474136&aid=768543&group_id=54559