[
https://issues.apache.org/jira/browse/CAMEL-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241128#comment-13241128
]
Claus Ibsen commented on CAMEL-604:
-----------------------------------
Jurgen I suggest to use the Camel mailing list / forum for help with Camel, and
*not* comment on old JIRA tickets.
And read on the Camel JMS wiki page, it talks about some cache level options
you can adjust to your needs. And on the user forum there is many people using
Camel with IBM MQ and you can find some threads about this as well.
> New JMS connection being created for every message
> --------------------------------------------------
>
> Key: CAMEL-604
> URL: https://issues.apache.org/jira/browse/CAMEL-604
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 1.3.0
> Reporter: Eric Levin
> Fix For: 1.4.0
>
> 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.
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
