L.S.,
When I connect to WebSphere MQ, I use com.ibm.mq.jms.MQConnectionFactory
instead of MQQueueConnectionFactory...
Gert
carmichs wrote:
Hi,
Thanks for the sample. I really appreciate the help. However, I am
getting the following exception and I can't seem to get the JMS binding
component to connect to the MQSeries queue.
INFO - ServiceUnitLifeCycle - Starting service unit:
jbi_jms_bc_su
Exception in thread "Timer-4" java.lang.AbstractMethodError:
com.ibm.mq.jms.MQQueueConnectionFactory.createConnection()Ljavax/jms/Connection;
at
org.apache.servicemix.jms.AbstractJmsProcessor.start(AbstractJmsProcessor.java:74)
at
org.apache.servicemix.soap.SoapEndpoint.activate(SoapEndpoint.java:348)
at
org.apache.servicemix.common.ServiceUnit.start(ServiceUnit.java:55)
at
org.apache.servicemix.common.BaseServiceUnitManager.start(BaseServiceUnitManager.java:151)
at
org.apache.servicemix.jbi.framework.ServiceUnitLifeCycle.start(ServiceUnitLifeCycle.java:103)
Here is my configuration:
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns:jms="http://servicemix.apache.org/jms/1.0";
xmlns:ebx="http://www.synoran.com/sde/se";>
<!-- Define an additional classpath location
for wsdl resources -->
<classpath>
<location>.</location>
</classpath>
<jms:endpoint service="ebx:SDEService"
endpoint="mq"
targetService="ebx:SDEService"
targetEndpoint="myConsumer"
role="consumer"
destinationStyle="queue"
jmsProviderDestinationName="SERVICEMIX.RQ"
connectionFactory="#connectionFactory"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out";
defaultOperation="ebx:executeDocument" />
<bean id="connectionFactory"
class="com.ibm.mq.jms.MQQueueConnectionFactory">
<property name="transportType" value="1"/>
<property name="queueManager" value="EBX5DEV" />
<property name="hostName" value="172.16.9.209" />
<property name="channel" value="CL0001" />
<property name="port" value="1414" />
</bean>
</beans>
anshukpal wrote:
Hi,
The below configuration might help you out in consuming the message from
the mqueue. It did work for me.
I have deployed that as a xbean component.
<jms:endpoint service="test:MyMQService"
endpoint="mq"
targetService="test:customComponent"
targetEndpoint="customComponent"
role="consumer"
destinationStyle="queue"
jmsProviderDestinationName="QUEUE_NAME"
connectionFactory="#connectionFactory"
defaultMep="http://www.w3.org/2004/08/wsdl/in-only";
/>
<bean id="connectionFactory"
class="com.ibm.mq.jms.MQQueueConnectionFactory">
<property name="transportType" value="1"/>
<property name="queueManager" value="QMGR_NAME" />
<property name="hostName" value="server_address" />
<property name="channel" value="QMGR_CHANNEL_NAME" />
<property name="port" value="1414" />
</bean>
Warm Regards,
Anshuk Pal Chaudhuri
-----Original Message-----
From: carmichs [mailto:[EMAIL PROTECTED]
Sent: Monday, August 20, 2007 9:23 PM
To: [email protected]
Subject: JMS Binding component from MQSeries
Hi,
Does anyone have a configuration example of connecting a jms binding
component to MQSeries?
I am trying to pick up a message off of an MQSeries v5.3 queue to pass
on to
our service engine.
I have an example of the same thing using ActiveMQ working on the
frontend,
but can't seem to figure out how to modify the configuration options to
use
MQSeries as the external resource. I have referred to the JMS Binding
conmponent doc where the properties are defined, but can't seem to match
those up with the MQ jndi settings I need.
Below is what I am trying to do
client --> MQSeries queue --> jms binding component --> nmr --> jsr181
service engine
Any help is greatly appreciated.
Thanks!
Steve
--
View this message in context:
http://www.nabble.com/JMS-Binding-component-from-MQSeries-tf4299709s1204
9.html#a12238485
Sent from the ServiceMix - User mailing list archive at Nabble.com.
**************** CAUTION - Disclaimer *****************
This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended
solely for the use of the addressee(s). If you are not the intended
recipient, please notify the sender by e-mail and delete the original
message. Further, you are not to copy, disclose, or distribute this e-mail
or its contents to any other person and any such actions are unlawful.
This e-mail may contain viruses. Infosys has taken every reasonable
precaution to minimize this risk, but is not liable for any damage you may
sustain as a result of any virus in this e-mail. You should carry out your
own virus checks before opening the e-mail or attachment. Infosys reserves
the right to monitor and review the content of all messages sent to or
from this e-mail address. Messages sent to or from this e-mail address may
be stored on the Infosys e-mail system.
***INFOSYS******** End of Disclaimer ********INFOSYS***
