You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Alain Knaff (JIRA)" <ji...@apache.org> on 2006/09/21 13:19:23 UTC

[jira] Created: (SM-590) Occasionnally, loanbroker example hangs in requestor.close()

Occasionnally, loanbroker example hangs in requestor.close()
------------------------------------------------------------

                 Key: SM-590
                 URL: https://issues.apache.org/activemq/browse/SM-590
             Project: ServiceMix
          Issue Type: Bug
          Components: servicemix-jms
    Affects Versions: 3.0
         Environment: Fedora Core 5, Linux 2.6.13-15.8, jre-1.4.2.11-11.1
            Reporter: Alain Knaff


Once every ten requests (approximatively), the Loan Broker client hangs on closing of the request. Once a hang has happened, and after Ctrl-C'ing the client, the next attempt fails with the following error:

     [java] WARN  - MultiplexingRequestor          - Response received for unknown request: ActiveMQTextMessage {commandId = 50, responseRequired = true, messageId = ID:aknaffpc-39340-1158760925808-6:0:2:1:22, originalDestination = null, originalTransactionId = null, producerId = ID:aknaffpc-39340-1158760925808-6:0:2:1, destination = queue://demo.org.servicemix.output, transactionId = null, expiration = 0, timestamp = 1158761596414, arrival = 0, correlationId = 1, replyTo = null, persistent = true, type = null, priority = 4, groupID = null, groupSequence =0, targetConsumerId = null, compressed = false, userID = null, content = org.apache.activeio.packet.ByteSequence@d0af9b, marshalledProperties = org.apache.activeio.packet.ByteSequence@b8f8eb, dataStructure = null, redeliveryCounter = 1, size = 0, properties = null, readOnlyProperties = true, readOnlyBody = true, text = null}

After changing the client code so as to use a random name for the reply queue:

 String returnQ="demo.org.servicemix.output" +(int)(1000*Math.random());
 Destination outQueue = new ActiveMQQueue(returnQ);

... the hang on requestor.close() still happens, but now it no longer triggers the above-mentioned exception. However, another hang on close now happens much more frequently.


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