client listening for jmx notifications hangs services sendin

jj Oct 28, 2004 10:56 PM

I have a client that listens for jmx notifications using the RMINotificationListener. It works great, except for the fact that if I suspend my client, my service hangs in a socket read after having sent the notification. When I resume my client, the service either continues normally, or complains with some socket errors before continuing (depends on how long I suspend the client).

Server is JBoss 3.2.5 (default + my services). Client uses 3.2.5 jbossall-client.jar.

This is a show stopper problem for me. I'd appreciate any suggestions.

Thanks in advance,
jj

1. Re: client listening for jmx notifications hangs services se

dimitris Oct 29, 2004 2:13 AM (in response to jj)

What would be your desired behaviour? For the server to discart the connection to the faulty client?
Actions
2. Re: client listening for jmx notifications hangs services se

jj Oct 29, 2004 3:20 PM (in response to jj)

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.
Actions
3. Re: client listening for jmx notifications hangs services se

starksm64 Oct 29, 2004 3:50 PM (in response to jj)

The client passed to the jboss server can use a custom socket factory to setup a read timeout to prevent an unbounded wait on the socket. More generally there should be a pooled NotificationBroadcasterSupport implementation to allow asynchronous dispatch of the notifications. We might have something already there so look around.
Actions

Go to original post