[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-634) If Server is restarted, client leases IDs might be out of sync

[Tim Fox (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMESSAGING-634?page=all ]

Tim Fox closed JBMESSAGING-634.
-------------------------------

    Resolution: Out of Date

> If Server is restarted, client leases IDs might be out of sync
> --------------------------------------------------------------
>
>                 Key: JBMESSAGING-634
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-634
>             Project: JBoss Messaging
>          Issue Type: Bug
>            Reporter: Clebert Suconic
>             Fix For: Unscheduled
>
>
> This is the scenario I have:
> I start the server...
> I have clients opening/closing connections in a loop...
> I kill the server...
> (will ignore the errors on client until I get restarted)
> I restart the server....
> I will get a bunch of errors on client, regarding not being able to find ClientIds on Lease operations (Just WARNs)
> Kill the client...
> after some time.. .the server gets into an unexpected state, after we have seen this exception:
> 20:59:37,765 ERROR [STDERR] java.lang.NullPointerException
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211)
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease.access$300(Lease.java:39)
> 20:59:37,765 ERROR [STDERR]     at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:242)
> 20:59:37,765 ERROR [STDERR]     at java.util.TimerThread.mainLoop(Timer.java:512)
> 20:59:37,765 ERROR [STDERR]     at java.util.TimerThread.run(Timer.java:462)
> I consider the description of this JIRA issue very subjective, we should rename it as soon as we have found the real cause.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira