[esb-issues] [JBoss JIRA] Updated: (JBESB-2481) Client and server side JBM information can become out of sync
Kevin Conner (JIRA)
jira-events at lists.jboss.org
Thu Mar 19 11:08:46 EDT 2009
[ https://jira.jboss.org/jira/browse/JBESB-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kevin Conner updated JBESB-2481:
--------------------------------
Fix Version/s: 4.4 CP3
(was: 4.6)
Affects Version/s: 4.4 CP2
(was: 4.5)
> Client and server side JBM information can become out of sync
> -------------------------------------------------------------
>
> Key: JBESB-2481
> URL: https://jira.jboss.org/jira/browse/JBESB-2481
> Project: JBoss ESB
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Transports
> Affects Versions: 4.4 CP2
> Reporter: Kevin Conner
> Assignee: Kevin Conner
> Fix For: 4.4 CP3
>
>
> The issue appears to be occurring with the connection information and has been seen with a co-located (client and server in same VM) deployment.
> This may be indicative of a race condition, with the server side (even though co-located) deciding to close the connection at the same time as we access it.
> The result of this is the following
> Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id jr51-zktjeurf-1-wxm28srf-0fpqee-t2p1hs4
> at org.jboss.jms.wireformat.ConnectionCreateSessionDelegateRequest.serverInvoke(ConnectionCreateSessionDelegateRequest.java:84)
> at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
> at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866)
> at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608)
> at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:420)
> at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173)
> We should check for this during session creation and, if found, attempt to cleanup and re-establish the connection.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the esb-issues
mailing list