Re: Checking listener registrations

Jens,

> I have investigated a strange behavior:
>
> I have registered from a client to a remote MBeanServer via RMI. The client
> is running a scheduler which checks any 20 secs the connection to the MBean
> server (tries to find an mbean). If the server is not available the
> connection is thrown away and a new one is established. If I have stopped
> the Mbean server an restarted it within the 20 secs the scheduler does not
> recognize anything because the scheduler still can contact the server using
> the old connection. The only problem ist that its listener registration is
> lost and no notifications are sent to the client. Am I right ? If yes why is
> the old connection still valid and is it possible for the client to check
> for existing listener registrations ?

Is there any reason you use a scheduler instead of the built-in
heartbeat mechanism that both mx4j and jmxri have ?
Apart from that, the behavior you noticed it was on mx4j (J2SE 1.4) or
on jmxri (J2SE 5) ?
I find strange that RMI does not detect that the connection has gone
and the rmi stub is able to reconnect to a new server.
Have you already tried to reproduce this behavior with a simple RMI
client ? From your description does not seem related to JMX.

Regards,

Simon
-- 
http://bordet.blogspot.com

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642