There's a bunch of info on this page about that:
http://activemq.apache.org/jmstemplate-gotchas.html

In short, unless the javax.jms.ConnectionFactory object you're using is
using connection pooling, you need to do something special.

Is your ConnectionFactory an EJB-managed implementation? If you're on
WebSphere, it should be.


On 18 July 2014 12:12, Ali, Mohammad <[email protected]> wrote:

> Hi Matt,
>
> I am using camel-jms.
>
> Regards,
> Shadab
>
> -----Original Message-----
> From: Matt Sicker [mailto:[email protected]]
> Sent: Friday, July 18, 2014 10:17 PM
> To: Camel Users
> Subject: Re: JMS producer creating connection for every message causing
> performance issue
>
> Are you using camel-jms or camel-sjms?
>
>
> On 18 July 2014 08:39, Ali, Mohammad <[email protected]> wrote:
>
> > Hi,
> >
> > We are using camel JMS component(producer) to send message to IBM MQ
> > and using camel 2.9.0 version. We observe that JMS producer is
> > creating connection with every message which is hitting the
> > performance badly. Is there any option to set so that same connection
> > will be used for evary message?
> >
> >
> > Thanks & Regards,
> > Shadab
> >
> > This e-mail (and any attachments), is confidential and may be privileged.
> > It may be read, copied and used only
> > by intended recipients. Unauthorized access to this e-mail (or
> > attachments) and disclosure or copying of its contents or any action
> > taken in reliance on it is unlawful. Unintended recipients must notify
> > the sender immediately by e-mail/phone & delete it from their system
> > without making any copies or disclosing it to a third person.
> >
> >
>
>
> --
> Matt Sicker <[email protected]>
>
> This e-mail (and any attachments), is confidential and may be privileged.
> It may be read, copied and used only
> by intended recipients. Unauthorized access to this e-mail (or
> attachments) and disclosure or copying of its
> contents or any action taken in reliance on it is unlawful. Unintended
> recipients must notify the sender immediately
> by e-mail/phone & delete it from their system without making any copies or
> disclosing it to a third person.
>
>


-- 
Matt Sicker <[email protected]>

Reply via email to