Given the current implementation, discarding all of an unresponsive client's registrations after some configurable timeout is one solution. Scott has already fixed a related bug: http://www.jboss.org/index.html?module=bb&op=viewtopic&t=47243
Long term I suggest configurable transports for JMX notifications. As an immediate solution, we're going to write a JMX Notification broadcast service. Clients will delegate subscription for JMX Notifications to this service. The service will propagate notifications back to clients via a JMS topic. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3853326#3853326 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3853326 ------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
