camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jürgen Weber (Commented) (JIRA) <j...@apache.org>
Subject [jira] [Commented] (CAMEL-604) New JMS connection being created for every message
Date Thu, 29 Mar 2012 08:33:39 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13241080#comment-13241080
] 

Jürgen Weber commented on CAMEL-604:
------------------------------------

Is this bug/feature still present in Camel 1.9.1? We have to use Websphere MQ as JMS provider,
so using AMQ instead of generic JMS component is not a good workaround.
I did a trace of MQ within Camel, and there were indeed a lot of MQOPEN calls, so I guess
the problem is still there.
Effectively this bug makes the JMS component unusable, so the bug should be fixed.
                
> 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

       

Mime
View raw message