You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/02/17 07:16:40 UTC
[jira] Commented: (AMQ-2611) Stopping camel context with
ActiveMQComponent does not close connections to ActiveMQ
[ https://issues.apache.org/activemq/browse/AMQ-2611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=57609#action_57609 ]
Claus Ibsen commented on AMQ-2611:
----------------------------------
Aaron thanks for the patch. I have moved the ticket to AMQ as its a bug/issue with AMQ.
> Stopping camel context with ActiveMQComponent does not close connections to ActiveMQ
> ------------------------------------------------------------------------------------
>
> Key: AMQ-2611
> URL: https://issues.apache.org/activemq/browse/AMQ-2611
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.3.0
> Environment: Ubuntu Linux 9.10, Sun JDK 1.6.0_15, Camel 2.1.0-psc-01-00RC1, ActiveMQ 5.3.0-psc-01-00RC1
> Reporter: Aaron Riekenberg
> Attachments: ActiveMQTest.java, camel2469.patch
>
>
> Stopping a camel context that uses an ActiveMQComponent does not appear to close connections to the ActiveMQBroker. See the attached test case as an example. It creates a camel context containing an ActiveMQ consumer and producer, sends a message, then destroys the context. The test case does this in a loop so every 4 seconds the old camel context is destroyed and a new one is created. Every second the test outputs the number of connections to the ActiveMQ broker. This number continually grows over time. After running for a few minutes I see output like this:
> 10:17:28,885 INFO ActiveMQTest - num connections = 159
> 10:17:29,885 INFO ActiveMQTest - num connections = 159
> 10:17:30,574 INFO ActiveMQTest - creating context and sending message
> 10:17:30,574 INFO DefaultCamelContext - Apache Camel 2.1.0-psc-01-00RC1 (CamelContext:camel-160) is starting
> 10:17:30,574 INFO DefaultCamelContext - JMX enabled. Using DefaultManagedLifecycleStrategy.
> 10:17:30,744 INFO DefaultCamelContext - Apache Camel 2.1.0-psc-01-00RC1 (CamelContext:camel-160) started
> 10:17:30,753 INFO ActiveMQTest - consume message = message
> 10:17:30,885 INFO ActiveMQTest - num connections = 160
> 10:17:31,885 INFO ActiveMQTest - num connections = 160
> 10:17:32,747 INFO ActiveMQTest - destroying context
> 10:17:32,747 INFO DefaultCamelContext - Apache Camel 2.1.0-psc-01-00RC1 (CamelContext:camel-160) is stopping
> 10:17:32,755 INFO DefaultInflightRepository - Shutting down with no inflight exchanges.
> 10:17:32,755 INFO DefaultCamelContext - Apache Camel 2.1.0-psc-01-00RC1 (CamelContext:camel-160) stopped
> 10:17:32,886 INFO ActiveMQTest - num connections = 160
> 10:17:33,885 INFO ActiveMQTest - num connections = 160
> Also if I do "netstat -an | grep 61616" I see the number of connections to the broker on TCP port 61616 is continually growing.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.