Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (athena.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.213.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <3FB7635019A5CB408BAD3C2E108A4EEC0F0E9C2BEE@GCPWINHYD2EVS22.IND.CORP.AD>
References: 
 <3FB7635019A5CB408BAD3C2E108A4EEC0F0E7B299D@GCPWINHYD2EVS22.IND.CORP.AD>
 <CALvzYd-5XGeg1rFPTWK1vzAZwbPocOUb+VRkQJfVHMMQ+crmqg@mail.gmail.com>
 <3FB7635019A5CB408BAD3C2E108A4EEC0F0E85A932@GCPWINHYD2EVS22.IND.CORP.AD>
 <CALvzYd9=oHZYCLzX=DhT4z-Te7ZAjfS9sN=UvzQNA=MMnSE-QA@mail.gmail.com>
 <3FB7635019A5CB408BAD3C2E108A4EEC0F0E9C2BEE@GCPWINHYD2EVS22.IND.CORP.AD>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Thu, 7 Aug 2014 18:52:53 +0200
Message-ID: 
 <CAGB5yN=EwdH7ryBgT2TNVWq9_BPUKd5qEHUuFCFbduXhAtxyRg@mail.gmail.com>
Subject: Re: Multiple JMS producer with IBMMQ
To: "users@camel.apache.org" <users@camel.apache.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi

Its usually on the JMS client you should look first to optimize, such
as using a connection pool, and whether you need to use persistent
messaging or not, or if you can use async vs sync sending etc. All
that is often something you can configure on the JMS client level ->
in other words take a look at the IBM JMS client and tune it.

And a connection pool often speedup.

And for concurrent sending from Camel point of view, then make routing
concurrent. The best place to look is where the route starts, eg at
the consumer. Maybe you can enable concurrent consumers etc.


On Thu, Aug 7, 2014 at 5:57 PM, Ali, Mohammad <Mohammad.Ali5@genpact.com> w=
rote:
> Hi Christian,
>
> Thanks a lot for your response.
> I tried using the thread dsl, when I give the thread count as 5, I can se=
e in IBMMQ server there are 25 connection in output count, but rate at whic=
h messages pushed to the queue doesn't increase. It processes 2000 non-pers=
istence messages per minute which is very low earlier the rate was 1500msg/=
min. Is there any configuration to increase the message rate to send to the=
 queue? Or any suggestion on this, I googled but doesn't find any solution.
>
> Regards,
> Shadab
>
>
> -----Original Message-----
> From: Christian M=C3=BCller [mailto:christian.mueller@gmail.com]
> Sent: Tuesday, August 05, 2014 12:35 PM
> To: users@camel.apache.org
> Subject: Re: Multiple JMS producer with IBMMQ
>
> Hi Shadab!
>
> Sorry, I overlooked that you are talking about the producer.
> What is the source you are reading from?
> And may the thread() DSL element is helpful for you:
>
> from("xxx")
>    .threads(3, 10, "threadName")
>    .to("xxx");
>
>
> Best,
>
> Christian
> -----------------
>
> Software Integration Specialist
>
> Apache Member
> V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer Apac=
he Incubator PMC Member
>
> https://www.linkedin.com/pub/christian-mueller/11/551/642
>
>
> On Tue, Aug 5, 2014 at 8:26 AM, Ali, Mohammad <Mohammad.Ali5@genpact.com>
> wrote:
>
>> Hi Christian,
>>
>> Thanks for your reply.
>>
>> Will concurrentConsumer option work for producer also? I will give a
>> try to this.
>>
>> Regards,
>> Shadab
>>
>>
>> -----Original Message-----
>> From: Christian M=C3=BCller [mailto:christian.mueller@gmail.com]
>> Sent: Tuesday, August 05, 2014 1:40 AM
>> To: users@camel.apache.org
>> Subject: Re: Multiple JMS producer with IBMMQ
>>
>> Is the concurrentConsumer option not working for you?
>>
>> Best,
>> Christian
>> Am 04.08.2014 18:02 schrieb "Ali, Mohammad" <Mohammad.Ali5@genpact.com>:
>>
>> > Hi,
>> >
>> > I am using camel-2.9.0. JMS producer component with IBMMQ
>> > performance is very slow, I want to create multiple JMS producer to
>> > send message to IBM queue something like multi-threading. Is there a
>> > way in camel where I can create multiple threads of JMS producer,
>> > just like
>> concurrent consumers.
>> >
>> >
>> > Thanks,
>> > Shadab
>> >
>> > This e-mail (and any attachments), is confidential and may be privileg=
ed.
>> > 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.
>> >
>> >
>>
>> 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.
>>
>>
>
> 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 attachment=
s) and disclosure or copying of its
> contents or any action taken in reliance on it is unlawful. Unintended re=
cipients must notify the sender immediately
> by e-mail/phone & delete it from their system without making any copies o=
r disclosing it to a third person.
>


--=20
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/