[jboss-jira] [JBoss JIRA] Commented: (JBMESSAGING-812) "Cannot find object in dispatcher..." intermittent failures

[Tim Fox (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBMESSAGING-812?page=comments#action_12352313 ] 
            
Tim Fox commented on JBMESSAGING-812:
-------------------------------------

The error occurs for the following reason.

A test creates a connection then exits for some reason without closing the connection.

The test completes and another test starts, restarting the server peer and resetting the object id counter.

A new different object is created with the same object id of the old object.

Eventually remoting times out the old connection since it has not received a ping.

It closes the connection and the connection (or one of it's sessions/consumers) unregisters itself from the dispatcher, but this ends up removing the newer object which has the same id.

A request comes in for the newer object and it cannot find it and an exception is thrown.

I have added a sanity check to the Dispatcher so when it deregisters it checks to see if the object being deregistered is actually the same object as the one that was orginally registered If not then it logs a warning and ignores the operation.

> "Cannot find object in dispatcher..." intermittent failures
> -----------------------------------------------------------
>
>                 Key: JBMESSAGING-812
>                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-812
>             Project: JBoss Messaging
>          Issue Type: Bug
>    Affects Versions: 1.2.0.Beta1
>            Reporter: Tim Fox
>         Assigned To: Tim Fox
>            Priority: Critical
>             Fix For: 1.2.0.CR1
>
>         Attachments: cannot_find_object.log
>
>
> Intermittently when running the test suite in remote socket mode (and http?) we obtain errors as invocations hit the server but the target object cannot be found.
> After inspecting the logs it seems the JBoss Remoting is detecting a problem on an actually healthy connection, causing it to be closed. The connection is actually still alive and some time later the client makes an invocation resulting in the target object not being found.
> See attached logs.
> I will be running with remoting trace, to get more info sine the logs do not have enough information as to why remoting thinks the connection has a problem.

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