From: jj <nu...@jb...> - 2004-10-29 19:20:09
|
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 |