[mule-user] [mule 2.0.0] How to configure jms:websphere-connector
L.Depauw
Hi,
I'm trying to configure a ibm jms websphere connector in mule 2.0.0. The
connection should be of the client type -> "transportType" value="1"
This is my config:
<!-- Set up IBM MQ -->
<jms:websphere-connector name="websphereConnector"
connectionFactory-ref="MQConnectionFactory">
</jms:websphere-connector>
<spring:bean id="MQConnectionFactory"
class="com.ibm.mq.jms.MQQueueConnectionFactory">
<properties>
<spring:entry key="hostName" value="999999"/>
<spring:entry key="port" value="99999"/>
<spring:entry key="queueManager" value="QM.999"/>
<spring:entry key="transportType" value="1"/>
<spring:entry key="useConnectionPooling" value="true"/>
</properties>
</spring:bean>
After starting the mule server I get this error:
Root Exception stack trace:
java.lang.UnsatisfiedLinkError: no mqjbnd05 in java.library.path
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1682)
at java.lang.Runtime.loadLibrary0(Runtime.java:822)
at java.lang.System.loadLibrary(System.java:993)
at com.ibm.mq.MQSESSION.loadLib(MQSESSION.java:865)
at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:227)
at java.security.AccessController.doPrivileged(Native Method)
at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:221)
at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:68)
at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:493)
at
com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
155)
at
com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
tion(MQBindingsManagedConnectionFactoryJ11.java:153)
at
com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
ion(MQBindingsManagedConnectionFactoryJ11.java:189)
at
com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
a:80)
at
com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
ctionManager.java:171)
at
com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
a:754)
at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:688)
at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:469)
at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:2248)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1749)
at
com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:144)
at
com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:54)
at
com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueue
ConnectionFactory.java:106)
at
com.ibm.mq.jms.MQQueueConnectionFactory.createConnection(MQQueueConne
ctionFactory.java:954)
at
org.mule.transport.jms.Jms11Support.createConnection(Jms11Support.jav
a:54)
at
org.mule.transport.jms.JmsConnector.createConnection(JmsConnector.jav
a:211)
at
org.mule.transport.jms.JmsConnector.doConnect(JmsConnector.java:284)
at
org.mule.transport.AbstractConnector.connect(AbstractConnector.java:1
353)
at
org.mule.transport.SingleAttemptConnectionStrategy.doConnect(SingleAt
temptConnectionStrategy.java:25)
at
org.mule.transport.AbstractConnectionStrategy.connect(AbstractConnect
ionStrategy.java:108)
at
org.mule.transport.AbstractConnector.connect(AbstractConnector.java:1
362)
at
org.mule.transport.SingleAttemptConnectionStrategy.doConnect(SingleAt
temptConnectionStrategy.java:25)
at
org.mule.transport.AbstractConnectionStrategy.connect(AbstractConnect
ionStrategy.java:108)
at
org.mule.transport.AbstractConnector.start(AbstractConnector.java:392
)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.mule.lifecycle.DefaultLifecyclePhase.applyLifecycle(DefaultLifecy
clePhase.java:272)
at
org.mule.lifecycle.DefaultLifecyclePhase.fireLifecycle(DefaultLifecyc
lePhase.java:143)
at
org.mule.lifecycle.GenericLifecycleManager.firePhase(GenericLifecycle
Manager.java:79)
at org.mule.DefaultMuleContext.start(DefaultMuleContext.java:147)
at org.mule.MuleServer.run(MuleServer.java:254)
at org.mule.MuleServer.start(MuleServer.java:239)
at
org.mule.module.boot.MuleServerWrapper.start(MuleServerWrapper.java:4
8)
at
org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:
2788)
When I search on google for this missing lib it is caused due to the factory
tries to make a binding to the server installation but I need a client
binding. So for some reason the "transportType" is not 1.
I am a newbie with mq series so any help would be appriciated, someone got a
working 2.0.0 config ?
Thanks
Luc De pauw
--
View this message in context: http://www.nabble.com/-mule-2.0.0--How-to-configure-jms%3Awebsphere-connector-tp17253398p17253398.html
Sent from the Mule - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Steve Olson
My understanding of IBM's JMS driver with MQ V6.0.x is that all transport
types (client or local) use JNI to leave the JMS drivers and leverage the MQ
install on the local box. So no matter whether you are talking to a local
queue manager (which supports XA etc), or a remote one using the client, you
still have to have the path to the MQ dlls available to your JVM running
mule. The dlls required are in the java/lib subdirectory of whichever MQ
install you are using.
--
View this message in context: http://www.nabble.com/-mule-2.0.0--How-to-configure-jms%3Awebsphere-connector-tp17253398p17254304.html