Patches item #914578, was opened at 2004-03-12 00:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=914578&group_id=22866
Category: JBossServer Group: v3.2 Status: Open Resolution: None Priority: 5 Submitted By: Rob Dickinson (rob_dickinson) Assigned to: Nobody/Anonymous (nobody) Summary: Expiring unreachable JMX notification listeners Initial Comment: The implementation of JMX notifications in JBoss works quite well, assuming that notification listeners never disconnect unexpectedly. If a notification listener becomes unreachable (if it dies without unregistering itself), the JBoss server will still attempt to contact the listener every time a new notification is sent out. This can bog down performance, as each notification sent may involve many socket timeouts. This patch to NotificationBroadcasterSupport removes notification listeners that fail due to a ConnectException. This minor change works fine for our purposes. A more generic patch might allow other exception classes (other than just ConnectException) to trigger a removal, or to remove a listener after x failures (here a single failure is enough to warrant expiration). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376687&aid=914578&group_id=22866 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
