[ mx4j-Bugs-902819 ] Fetcher thread in RemoteNotificationClientHandler never ends
"SourceForge.net" <[email protected]>
| Newsgroups | gmane.comp.java.mx4j.devel |
|---|---|
| Message-ID | <[email protected]> |
Bugs item #902819, was opened at 2004-02-23 11:56 Message generated for change (Settings changed) made by btscully You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=450647&aid=902819&group_id=47745 Category: JSR 160 Implementation Group: Release 2.0.0 Status: Open >Resolution: Accepted Priority: 5 Submitted By: Chris Arrington (cdarring) >Assigned to: Brian Scully (btscully) Summary: Fetcher thread in RemoteNotificationClientHandler never ends Initial Comment: Submitter: Chris Arrington ([email protected]) Summary: RemoteNotificationClientHandler fetcher thread for remote notifications does not end after JMXConnectorServer is shutdown either gracefully or forcefully, using MX4J 2.0 beta 1. Detail: When NotificationListeners are added via a remote MBeanServerConnection, tuples are added to a local Map with the listener objects. A fetcher thread is then started that polls the JMXConnectorServer periodically for notifications. This thread is ended ONLY as soon as all NotificationListeners are removed (RemoteNotificationClientHandler.java lines 133-135), based on the number of tuples (NotificationListener objects) in the Map. Ending the fetcher thread means that the user must be able to detect the lost connection, have all references to the NotificationListeners, and remove them all upon detecting the lost connection. Even if the user were able to detect the lost connection, the order of calls in ClientInvoker (lines 91- 92) is such that the remote processing is called before the local processing which removes the NotificationTuples, which is what will allow for the ending of the fetcher thread. However, when the JMXConnectorServer is no longer up, the removal will not proceed past the remote processing, and the NotificationListeners cannot be removed. At the very least, if remote and local processing were reversed, there would be a possibility for ending the fetcher thread. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=450647&aid=902819&group_id=47745 ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click