[jira] Resolved: (CAMEL-604) New JMS connection being created for every message

["James Strachan (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/CAMEL-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Strachan resolved CAMEL-604.
----------------------------------

    Resolution: Won't Fix

As Claus said, if you use the activemq component directly - which is what we recommend if you are using ActiveMQ - rather than the JMS component everything works fine.

See the blue info box on the JMS page which describes your issue and why you should use the ActiveMQ component - or explicitly use a JMS pool wrapper around the ActiveMQ connection factory
http://activemq.apache.org/camel/jms.html

Its easier to just use the ActiveMQ component as that does the right thing for you
http://activemq.apache.org/camel/activemq.html


> New JMS connection being created for every message
> --------------------------------------------------
>
>                 Key: CAMEL-604
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-604
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-jms
>    Affects Versions: 1.3.0
>            Reporter: Eric Levin
>         Attachments: ActiveMQ-Camel-Test.zip, after 130 messages being sent.jpg, falsealarm.jpg
>
>
> A new connection is being created / shutdown for every message that is sent through my ActiveMQ JMSComponent.  I thought this issue had been resolved for Camel 1.3; however, as shown within the example project, it doesn't seem to be.  This is very concerning for rapidly produced messages as there is alot of overhead with creating a new connection.
> Forum posting on this issue: http://www.nabble.com/New-connection-being-created-for-every-message-(post-1.3-camel)-td17684874s22882.html
> Steps to running the attached sample:
> -Have an instance of ActiveMQ running (localhost to the test app) with openwire exposed on port 61616 (the default port)
> -After extracting the example project, simply run 'mvn test' and it will begin sending messages through Camel
> -Open JConsole and look under the Connections for localhost broker - you will notice the suffix on connections increasing very quickly as connections are being opened/torn down for every message sent from the test app.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.