You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Mikael Finstad (Created) (JIRA)" <ji...@apache.org> on 2012/03/12 11:00:38 UTC

[jira] [Created] (AMQ-3761) Temp queues hanging after a while

Temp queues hanging after a while
---------------------------------

                 Key: AMQ-3761
                 URL: https://issues.apache.org/jira/browse/AMQ-3761
             Project: ActiveMQ
          Issue Type: Bug
    Affects Versions: 5.5.1
            Reporter: Mikael Finstad
         Attachments: ActiveMQTempQueueTest.cs

When using temp queues, after a while, methods on it will start hanging. I have attached a test case which will reproduce the problem.
Requires NUnit framework, Apache.NMS and Apache.NMS.ActiveMQ.
Note1: This is also happening with JMS in our field test environment, so it does not seem to be related to NMS
Note2: We are actually not using NMS/JMS API directly like in this test, but we are using spring framework (.net) with MessageListenerContainer and NmsTemplate on top, so excuse me if my code is not quite good, I had to quickly rewrite it to reproduce the problem directly with NMS only.

Take a look in the activemq web gui under "Messages Dequeued", and start the test.
It will run for some hundred messages, and then hang , sometimes on CreateTemporaryQueue(), sometimes on CreateConsumer(tempQueue) (pause execution to see) and sometimes an exception is thrown on tempQueue.Delete (Exception of type 'Apache.NMS.NMSConnectionException' was thrown.) with InnerException null.

If you try to comment out "tempQueue = session2.CreateTemporaryQueue();" and uncomment "tempQueue = SessionUtil.GetDestination(session2, "testqueue.response");" you will see that it runs for thousands of messages without any problems.
We have switched to using permanent queues like this (with correlationId) in our test environment now, and it seems to be working fine. But I thought I'd report it so that you know about it.


Versions:
Apache.NMS.ActiveMQ 1.5.3
Apache.NMS 1.5.0
ActiveMQ 5.5.1 (also tried 5.5.1 02-02 from fusesource)


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Moved] (AMQNET-374) Temp queues hanging after a while

Posted by "Timothy Bish (Moved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQNET-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish moved AMQ-3761 to AMQNET-374:
------------------------------------------

    Affects Version/s:     (was: 5.5.1)
                       1.5.2
                       1.5.3
                  Key: AMQNET-374  (was: AMQ-3761)
              Project: ActiveMQ .Net  (was: ActiveMQ)
    
> Temp queues hanging after a while
> ---------------------------------
>
>                 Key: AMQNET-374
>                 URL: https://issues.apache.org/jira/browse/AMQNET-374
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>    Affects Versions: 1.5.3, 1.5.2
>            Reporter: Mikael Finstad
>             Fix For: 1.5.4
>
>         Attachments: ActiveMQTempQueueTest.cs
>
>
> When using temp queues, after a while, methods on it will start hanging. I have attached a test case which will reproduce the problem.
> Requires NUnit framework, Apache.NMS and Apache.NMS.ActiveMQ.
> Note1: This is also happening with JMS in our field test environment, so it does not seem to be related to NMS
> Note2: We are actually not using NMS/JMS API directly like in this test, but we are using spring framework (.net) with MessageListenerContainer and NmsTemplate on top, so excuse me if my code is not quite good, I had to quickly rewrite it to reproduce the problem directly with NMS only.
> Take a look in the activemq web gui under "Messages Dequeued", and start the test.
> It will run for some hundred messages, and then hang , sometimes on CreateTemporaryQueue(), sometimes on CreateConsumer(tempQueue) (pause execution to see) and sometimes an exception is thrown on tempQueue.Delete (Exception of type 'Apache.NMS.NMSConnectionException' was thrown.) with InnerException null.
> If you try to comment out "tempQueue = session2.CreateTemporaryQueue();" and uncomment "tempQueue = SessionUtil.GetDestination(session2, "testqueue.response");" you will see that it runs for thousands of messages without any problems.
> We have switched to using permanent queues like this (with correlationId) in our test environment now, and it seems to be working fine. But I thought I'd report it so that you know about it.
> Versions:
> Apache.NMS.ActiveMQ 1.5.3
> Apache.NMS 1.5.0
> ActiveMQ 5.5.1 (also tried 5.5.1 02-02 from fusesource)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Updated] (AMQ-3761) Temp queues hanging after a while

Posted by "Mikael Finstad (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mikael Finstad updated AMQ-3761:
--------------------------------

    Attachment: ActiveMQTempQueueTest.cs
    
> Temp queues hanging after a while
> ---------------------------------
>
>                 Key: AMQ-3761
>                 URL: https://issues.apache.org/jira/browse/AMQ-3761
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.5.1
>            Reporter: Mikael Finstad
>         Attachments: ActiveMQTempQueueTest.cs
>
>
> When using temp queues, after a while, methods on it will start hanging. I have attached a test case which will reproduce the problem.
> Requires NUnit framework, Apache.NMS and Apache.NMS.ActiveMQ.
> Note1: This is also happening with JMS in our field test environment, so it does not seem to be related to NMS
> Note2: We are actually not using NMS/JMS API directly like in this test, but we are using spring framework (.net) with MessageListenerContainer and NmsTemplate on top, so excuse me if my code is not quite good, I had to quickly rewrite it to reproduce the problem directly with NMS only.
> Take a look in the activemq web gui under "Messages Dequeued", and start the test.
> It will run for some hundred messages, and then hang , sometimes on CreateTemporaryQueue(), sometimes on CreateConsumer(tempQueue) (pause execution to see) and sometimes an exception is thrown on tempQueue.Delete (Exception of type 'Apache.NMS.NMSConnectionException' was thrown.) with InnerException null.
> If you try to comment out "tempQueue = session2.CreateTemporaryQueue();" and uncomment "tempQueue = SessionUtil.GetDestination(session2, "testqueue.response");" you will see that it runs for thousands of messages without any problems.
> We have switched to using permanent queues like this (with correlationId) in our test environment now, and it seems to be working fine. But I thought I'd report it so that you know about it.
> Versions:
> Apache.NMS.ActiveMQ 1.5.3
> Apache.NMS 1.5.0
> ActiveMQ 5.5.1 (also tried 5.5.1 02-02 from fusesource)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] [Resolved] (AMQNET-374) Temp queues hanging after a while

Posted by "Timothy Bish (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQNET-374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQNET-374.
---------------------------------

       Resolution: Duplicate
    Fix Version/s: 1.5.4
         Assignee: Timothy Bish

This is fixed in trunk and the 1.5.x fixes branch.
                
> Temp queues hanging after a while
> ---------------------------------
>
>                 Key: AMQNET-374
>                 URL: https://issues.apache.org/jira/browse/AMQNET-374
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>    Affects Versions: 1.5.2, 1.5.3
>            Reporter: Mikael Finstad
>            Assignee: Timothy Bish
>             Fix For: 1.5.4
>
>         Attachments: ActiveMQTempQueueTest.cs
>
>
> When using temp queues, after a while, methods on it will start hanging. I have attached a test case which will reproduce the problem.
> Requires NUnit framework, Apache.NMS and Apache.NMS.ActiveMQ.
> Note1: This is also happening with JMS in our field test environment, so it does not seem to be related to NMS
> Note2: We are actually not using NMS/JMS API directly like in this test, but we are using spring framework (.net) with MessageListenerContainer and NmsTemplate on top, so excuse me if my code is not quite good, I had to quickly rewrite it to reproduce the problem directly with NMS only.
> Take a look in the activemq web gui under "Messages Dequeued", and start the test.
> It will run for some hundred messages, and then hang , sometimes on CreateTemporaryQueue(), sometimes on CreateConsumer(tempQueue) (pause execution to see) and sometimes an exception is thrown on tempQueue.Delete (Exception of type 'Apache.NMS.NMSConnectionException' was thrown.) with InnerException null.
> If you try to comment out "tempQueue = session2.CreateTemporaryQueue();" and uncomment "tempQueue = SessionUtil.GetDestination(session2, "testqueue.response");" you will see that it runs for thousands of messages without any problems.
> We have switched to using permanent queues like this (with correlationId) in our test environment now, and it seems to be working fine. But I thought I'd report it so that you know about it.
> Versions:
> Apache.NMS.ActiveMQ 1.5.3
> Apache.NMS 1.5.0
> ActiveMQ 5.5.1 (also tried 5.5.1 02-02 from fusesource)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira