Return-Path: 
 <users-return-56479-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 43F91187FE
	for <apmail-camel-users-archive@www.apache.org>;
 Wed, 29 Jul 2015 03:32:53 +0000 (UTC)
Received: (qmail 94865 invoked by uid 500); 29 Jul 2015 03:32:52 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 94817 invoked by uid 500); 29 Jul 2015 03:32:52 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 94806 invoked by uid 99); 29 Jul 2015 03:32:52 -0000
Received: from Unknown (HELO spamd4-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Jul 2015 03:32:52 +0000
Received: from localhost (localhost [127.0.0.1])
	by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org)
 with ESMTP id B24E3C0337
	for <users@camel.apache.org>; Wed, 29 Jul 2015 03:32:51 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: 4.313
X-Spam-Level: ****
X-Spam-Status: No, score=4.313 tagged_above=-999 required=6.31
	tests=[HTML_MESSAGE=3, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01,
	T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001, URI_HEX=1.313]
	autolearn=disabled
Received: from mx1-eu-west.apache.org ([10.40.0.8])
	by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new,
 port 10024)
	with ESMTP id POG2iIWTLUPL for <users@camel.apache.org>;
	Wed, 29 Jul 2015 03:32:45 +0000 (UTC)
Received: from smtpout01-ttc.target.com (smtpout03.target.com
 [161.225.129.10])
	by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with
 ESMTPS id 5A971254A6
	for <users@camel.apache.org>; Wed, 29 Jul 2015 03:32:44 +0000 (UTC)
Received: from tettsdlp8p.hq.target.com (HELO TEEMAIL01P.hq.target.com)
 ([10.66.182.44])
  by smtpout01-ttc.target.com with ESMTP; 28 Jul 2015 22:02:38 -0500
Received: from TEEMAIL19P.hq.target.com ([fe80::c40d:563a:ec25:c528]) by
 TEEMAIL01P.hq.target.com ([fe80::cd0d:9a14:6bb1:5f9d%23]) with mapi id
 14.03.0195.001; Tue, 28 Jul 2015 22:31:36 -0500
From: Vanshul.Chawla <Vanshul.Chawla@target.com>
To: "users@camel.apache.org" <users@camel.apache.org>
Subject: RE: JMS MQ performance improvement
Thread-Topic: JMS MQ performance improvement
Thread-Index: AdChy3vMuj6Vk2qKSOuglq6MR0zLSgAK2DeAAApEG9AAKE7rgAmmo6qAABTIk2A=
Date: Wed, 29 Jul 2015 03:31:36 +0000
Message-ID: 
 <941A21E04BB7F54FA4C71A5379B04769193173FB@TEEMAIL19P.hq.target.com>
References: <941A21E04BB7F54FA4C71A5379B04769DCB48D@TCEMAIL17P.hq.target.com>
 <1433755483148-5767965.post@n5.nabble.com>
 <941A21E04BB7F54FA4C71A5379B04769DCB4C3@TCEMAIL17P.hq.target.com>
 <1433842369123-5768016.post@n5.nabble.com>
 <1438086895325-5770010.post@n5.nabble.com>
In-Reply-To: <1438086895325-5770010.post@n5.nabble.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.92.245.173]
Content-Type: multipart/alternative;
	boundary="_000_941A21E04BB7F54FA4C71A5379B04769193173FBTEEMAIL19Phqtar_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected

--_000_941A21E04BB7F54FA4C71A5379B04769193173FBTEEMAIL19Phqtar_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

To increase performance, use caching of connection. We used the same and ar=
e able to process a huge volume.



<!-- Queue Manager Connection factory(s) -->

  <bean id=3D"wmqConnectionFactory1-Prod1-FIT" class=3D"com.ibm.mq.jms.MQQu=
eueConnectionFactory">

    <property name=3D"CCDTURL">

      <bean class=3D"com.tgt.tcom.il.financial.MQConnectionFactoryUtil"

                                                                factory-met=
hod=3D"convert">

        <argument value=3D"${financial.WMQ.CCDTfile}" />

      </bean>

    </property>

    <property name=3D"queueManager" value=3D"${financial.WMQ.QMGrpName1}" /=
>



  </bean>

  <!-- Cache Connection Factory -->



  <bean id=3D"cachingWmqConnectionFactory1-Prod1-FIT"

                                class=3D"org.springframework.jms.connection=
.CachingConnectionFactory"

                                destroy-method=3D"destroy">

    <property name=3D"targetConnectionFactory" ref=3D"wmqConnectionFactory1=
-Prod1-FIT" />

    <property name=3D"cacheConsumers" value=3D"true" />

    <property name=3D"reconnectOnException" value=3D"true" />

    <property name=3D"sessionCacheSize" value=3D"10" />

  </bean>



  <!--Spring Transaction Manager -->



  <bean id=3D"wmqTransactionManager1-Prod1-FIT"

                                class=3D"org.springframework.jms.connection=
.JmsTransactionManager">

    <property name=3D"connectionFactory" ref=3D"wmqConnectionFactory1-Prod1=
-FIT" />

  </bean>



  <!--JMS components used for Endpoints -->

  <bean id=3D"wmq-qm1-Prod1-FIT" class=3D"org.apache.camel.component.jms.Jm=
sComponent">

    <property name=3D"connectionFactory" ref=3D"cachingWmqConnectionFactory=
1-Prod1-FIT" />

    <property name=3D"transactionManager" ref=3D"wmqTransactionManager1-Pro=
d1-FIT" />

    <property name=3D"transacted" value=3D"false" />

    <property name=3D"cacheLevelName" value=3D"CACHE_AUTO" />

    <property name=3D"concurrentConsumers" value=3D"${financial.WMQ.DWSub1.=
Consumers}" />

    <property name=3D"maxConcurrentConsumers" value=3D"${financial.WMQ.DWSu=
b1.MaxConsumers}" />

    <property name=3D"maxMessagesPerTask" value=3D"${financial.WMQ.DWSub1.m=
axMessagesPerTask}" />

  </bean>



Thanks and Regards,



Vanshul Chawla





-----Original Message-----
From: mytechnology [mailto:mytech1235@gmail.com]
Sent: Tuesday, July 28, 2015 6:05 PM
To: users@camel.apache.org
Subject: RE: JMS MQ performance improvement



Why is it so hard (so far impossible) to find a way of configuring connecti=
on pool with IBM MQ. All the documentation is with websphere MDBs or Active=
MQ and Camel.



Has any body used connection pool with IBM MQ and Camel?







--

View this message in context: http://camel.465427.n5.nabble.com/JMS-MQ-perf=
ormance-improvement-tp5767963p5770010.html

Sent from the Camel - Users mailing list archive at Nabble.com.

--_000_941A21E04BB7F54FA4C71A5379B04769193173FBTEEMAIL19Phqtar_--