[jboss-jira] [JBoss JIRA] Created: (JBMESSAGING-1109) Client-side race condition while closing connection

Ovidiu Feodorov (JIRA) jira-events at lists.jboss.org
Sat Oct 13 19:37:03 EDT 2007


Client-side race condition while closing connection
---------------------------------------------------

                 Key: JBMESSAGING-1109
                 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1109
             Project: JBoss Messaging
          Issue Type: Bug
    Affects Versions: 1.4.0.GA
            Reporter: Ovidiu Feodorov
         Assigned To: Tim Fox
            Priority: Minor


I've got this while receiving a large number of messages on 20 concurrent sessions (with receive())

@Thread-23 16:26:15,983 ERROR [ClientConsumer] Failed to send changeRate message
org.jboss.jms.exception.MessagingJMSException: Failed to invoke
        at org.jboss.jms.client.delegate.DelegateSupport.handleThrowable(DelegateSupport.java:247)
        at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:202)
        at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:157)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate.org$jboss$jms$client$delegate$ClientConsumerDelegate$changeRate$aop(ClientConsumerDelegate.java:138)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
        at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:107)
        at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
        at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
        at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate$changeRate_N952316153687074823.invokeNext(ClientConsumerDelegate$changeRate_N952316153687074823.java)
        at org.jboss.jms.client.delegate.ClientConsumerDelegate.changeRate(ClientConsumerDelegate.java)
        at org.jboss.jms.client.container.ClientConsumer.sendChangeRateMessage(ClientConsumer.java:703)
        at org.jboss.jms.client.container.ClientConsumer.checkStop(ClientConsumer.java:673)
        at org.jboss.jms.client.container.ClientConsumer.handleMessageInternal(ClientConsumer.java:659)
        at org.jboss.jms.client.container.ClientConsumer.access$000(ClientConsumer.java:54)
        at org.jboss.jms.client.container.ClientConsumer$1.run(ClientConsumer.java:271)
        at EDU.oswego.cs.dl.util.concurrent.QueuedExecutor$RunLoop.run(QueuedExecutor.java:89)
        at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id b6-n7zbrq7f-1-6ii5qq7f-onm5l5-31184a
        at org.jboss.jms.wireformat.ConsumerChangeRateRequest.serverInvoke(ConsumerChangeRateRequest.java:71)
        at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:144)
        at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:769)
        at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:573)
        at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:387)
        at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:166)
        at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:163)
        at org.jboss.remoting.Client.invoke(Client.java:1634)
        at org.jboss.remoting.Client.invoke(Client.java:548)
        at org.jboss.remoting.Client.invoke(Client.java:536)
        at org.jboss.jms.client.delegate.DelegateSupport.doInvoke(DelegateSupport.java:186)
        ... 17 more


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

        



More information about the jboss-jira mailing list