tag:blogger.com,1999:blog-8028068502920625891.post8484023322284521370..comments2023-05-17T06:20:23.203-07:00Comments on Ramblings on Open Source Integration: Camel Integration with WebSphere MQlcurryhttp://www.blogger.com/profile/01568142368502338154noreply@blogger.comBlogger15125tag:blogger.com,1999:blog-8028068502920625891.post-38169433492498763552017-05-22T05:06:47.308-07:002017-05-22T05:06:47.308-07:00File Not Found...Source code...Not available.File Not Found...Source code...Not available.Anonymoushttps://www.blogger.com/profile/09382596331648999602noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-19960308905299612882015-04-02T03:25:27.559-07:002015-04-02T03:25:27.559-07:00Hi,
I want to integrate the Apache camel jms with...Hi,<br /><br />I want to integrate the Apache camel jms with the IBM MQ without spring.<br />could you please let me know how to achevie.BHANU KODEhttps://www.blogger.com/profile/17929951247368224081noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-61239694188907466972014-12-01T11:27:22.345-08:002014-12-01T11:27:22.345-08:00I am using Camel 2.13 with SpringDSL. the "t...I am using Camel 2.13 with SpringDSL. the "to" element takes a URI in which the literal name of the Queue is loaded. However, WebsphereMQ allows queue names to be composite using QMGRname + Qname like "myQM/mqQ". However if I use the syntax with Camel, it fails. It tries to open a queue using the entire string as the queuename. WMQ's JMS docs explicitly define the above syntax as being their standard URI format (which I assumed Camel was passing through to". Anyone have any idea how to get QMGR name accepted as part of sending a message?cameleerhttps://www.blogger.com/profile/01832421470279084052noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-4924047421639656702014-01-24T00:20:52.445-08:002014-01-24T00:20:52.445-08:00Yep my bad :)
Let's go to test !!
ThxYep my bad :)<br />Let's go to test !!<br />ThxAnonymoushttps://www.blogger.com/profile/10433415732484274014noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-39500390634251196162014-01-22T13:08:49.068-08:002014-01-22T13:08:49.068-08:00hmm. Its a public link to dropbox so should be acc...hmm. Its a public link to dropbox so should be accessable without any special privs. Perhaps your corporate or firewall blocking? lcurryhttps://www.blogger.com/profile/01568142368502338154noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-36477418268295112642014-01-22T08:21:08.553-08:002014-01-22T08:21:08.553-08:00This comment has been removed by the author.Anonymoushttps://www.blogger.com/profile/10433415732484274014noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-90705908813772064422013-09-24T07:40:12.150-07:002013-09-24T07:40:12.150-07:00Since sharing this post I've discovered there ...Since sharing this post I've discovered there is some extra spring configuration you can add to solution to get more intelligent reuse of resources. We saw some unnecessary opening and closing of connections without the connection caching offered by the following configuration:<br /><br /><br /><br /><br /><br /> <bean id="wmqTransactionManager" class="org.springframework.jms.connection.JmsTransactionManager"><br /> <property name="connectionFactory" ref="wmqCachingConnectionFactory" /><br /> </bean> <br /> <br /> <!-- A cached connection to wrap the WMQ connection --> <br /> <bean id="wmqCachingConnectionFactory" class="org.springframework.jms.connection.CachingConnectionFactory"> <br /> <property name="targetConnectionFactory" ref="wmqConnectionFactory" /> <br /> <property name="sessionCacheSize" value="10" /> <br /> </bean><br /> <br /> <bean id="wmqConnectionFactory" class="com.ibm.mq.jms.MQQueueConnectionFactory"> <br /> <property name="transportType" value="${wmq.transporttype}"/><br /> <property name="hostName" value="${wmq.hostname}" /> <br /> <property name="port" value="${wmq.port}" /> <br /> <property name="queueManager" value="${wmq.queuemanager}" /> <br /> <property name="channel" value="${wmq.channel}" /> <br /> <property name="useConnectionPooling" value="${wmq.connectionpooled}" /> <br /> </bean><br /> <br /> <bean id="wmq" class="org.apache.camel.component.jms.JmsComponent"><br /> <property name="connectionFactory" ref="wmqCachingConnectionFactory"/><br /> <property name="transactionManager" ref="wmqTransactionManager"/><br /> <property name="transacted" value="${wmq.transacted}"/><br /> <property name="cacheLevelName" value="CACHE_CONSUMER" /><br /> </bean>lcurryhttps://www.blogger.com/profile/01568142368502338154noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-18642910375693439042013-09-24T07:32:53.092-07:002013-09-24T07:32:53.092-07:00This comment has been removed by the author.lcurryhttps://www.blogger.com/profile/01568142368502338154noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-88862091132887286122013-08-27T08:38:12.559-07:002013-08-27T08:38:12.559-07:00Known issue. This is fixed in version 7.0.1.6.Known issue. This is fixed in version 7.0.1.6.Anonymoushttps://www.blogger.com/profile/15123028152382358307noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-16900818456618733992013-01-29T07:10:13.568-08:002013-01-29T07:10:13.568-08:00Hi Manglu, I'm not sure if there is direct sup...Hi Manglu, I'm not sure if there is direct support for JNDI lookup in Camel but a very quick search shows one possible solution using a "destination name resolver" mentioned by Claus in the following trail http://camel.465427.n5.nabble.com/JMS-queue-JNDI-instead-of-physical-name-td494620.html<br />Haven't done it myself though. Good luck! and if i find anything else will let you know.lcurryhttps://www.blogger.com/profile/01568142368502338154noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-68200284206549990092013-01-28T21:11:00.818-08:002013-01-28T21:11:00.818-08:00Thanks. This stuff was helpful. Instead of using t...Thanks. This stuff was helpful. Instead of using the queue names can i look them up from the JNDI name space?Mangluhttps://www.blogger.com/profile/13845493871791689879noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-26245066536988374482012-10-16T12:00:58.886-07:002012-10-16T12:00:58.886-07:00I'm not sure about that error. haven't see...I'm not sure about that error. haven't seen that one. Sorry.If i think of anything i'll let you know.lcurryhttps://www.blogger.com/profile/01568142368502338154noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-31885340647265948612012-10-15T00:58:09.683-07:002012-10-15T00:58:09.683-07:00com.ibm.msg.client.osgi.wmq_7.0.1.3.jar deployment...com.ibm.msg.client.osgi.wmq_7.0.1.3.jar deployment leads to an error on my servicemix 4.4.1 OSGi container:<br /><br />org.osgi.framework.BundleException: R3 imports cannot contain directives.Dr. Martin Menzelhttps://www.blogger.com/profile/08108281043085713874noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-16967364625460884482011-02-11T07:23:45.033-08:002011-02-11T07:23:45.033-08:00This comment has been removed by the author.Olivier Rogerhttps://www.blogger.com/profile/13104465191310066645noreply@blogger.comtag:blogger.com,1999:blog-8028068502920625891.post-7346656316879325062011-02-07T02:36:54.675-08:002011-02-07T02:36:54.675-08:00Very instructive article. Thanks for sharing!Very instructive article. Thanks for sharing!Folkenhttps://www.blogger.com/profile/16809460378467010919noreply@blogger.com