[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-535) Possible race condition in initialization of the server-side Remoting callback client: "org.jboss.remoting.ServerInvoker$InvalidStateException: Can not process invocation request since is not in started state"

[Ovidiu Feodorov (JIRA)]

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

Ovidiu Feodorov closed JBMESSAGING-535.
---------------------------------------

    Resolution: Done

The root cause proved to be the fact that the server-side remoting callback handler associated with the remoting connection was not explicitly removed when the JMS Connection (and the associated JMSRemotingConnection instance) was being closed.

Most of the times the remoting Connector would have time to clear the hanging callback handlers, but sometimes when an "appclient" (remote) tests ran after a "servlet" (co-located) test, the remoting callback client would still use a hanging LocalClientInvoker pointing to a stopped server invoker, hence the "org.jboss.remoting.ServerInvoker$InvalidStateException: Can not process invocation request since is not in started state"

Fixed by explicitly removing the callback listener when stopping JMSRemotingConnection instance.


> Possible race condition in initialization of the server-side Remoting callback client: "org.jboss.remoting.ServerInvoker$InvalidStateException: Can not process invocation request since is not in started state"
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBMESSAGING-535
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-535
>             Project: JBoss Messaging
>          Issue Type: Bug
>          Components: JMS Remoting
>    Affects Versions: 1.0.1.CR4
>            Reporter: Ovidiu Feodorov
>         Assigned To: Ovidiu Feodorov
>            Priority: Critical
>             Fix For: 1.0.1.CR5
>
>         Attachments: appclient.log, server.log
>
>
> Shows up sporatically while running TCK tests. Condition usually goes away if the test is repeated.
> Logs attached.

-- 
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