Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

java.lang.UnsatisfiedLinkError: no mqjbnd05 in java.library.path

1,459 views
Skip to first unread message

Pepe

unread,
Jun 18, 2003, 5:51:41 PM6/18/03
to
Hi, I'm working with WSMQClient 5.3 and Eclipse 2.1 under redhat 9. When
I try to run the ASFClient1.java sample it crash with the excpetion:


Exception in thread "main" java.lang.UnsatisfiedLinkError: no mqjbnd05
in java.library.path at
java.lang.ClassLoader.loadLibrary(ClassLoader.java:1403) at
java.lang.Runtime.loadLibrary0(Runtime.java:788) at
java.lang.System.loadLibrary(System.java:832) at
com.ibm.mq.MQSESSION.loadLib(MQSESSION.java:818) at
com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:221) at
java.security.AccessController.doPrivileged(Native Method) at
com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:215) at
com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67) at
com.ibm.mq.MQSESSION.getSession(MQSESSION.java:455) at com.ibm.mq.MQMan-
agedConnectionJ11.<init>(MQManagedConnectionJ11.java:155) at com.ibm.mq-
MQBindingsManagedConnectionFactoryJ11._createManagedConnection(MQBindi-
ngsManagedConnectionFactoryJ11.java:153) at com.ibm.mq.MQBindingsManage-
dConnectionFactoryJ11.createManagedConnection(MQBindingsManagedConnecti-
onFactoryJ11.java:189) at com.ibm.mq.StoredManagedConnection.<init>(Sto-
redManagedConnection.java:80) at com.ibm.mq.MQSimpleConnectionManager.a-
llocateConnection(MQSimpleConnectionManager.java:171) at com.ibm.mq.MQQ-
ueueManager.obtainBaseMQQueueManager(MQQueueManager.java:737) at
com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:671) at
com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:452) at
com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52) at
com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1652) at
com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:1132) at
com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:170) at
com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:80) at
com.ibm.mq.jms.MQQueueConnectionFactory.createQueueConnection(MQQueueCo-
nnectionFactory.java:145) at ASFClient1.main(ASFClient1.java:81)


Any idea??? Thanks in advance. Pepe-

--
posted via MFF : http://www.MainFrameForum.com - USENET Gateway

RogerLacroix

unread,
Jun 19, 2003, 2:41:44 AM6/19/03
to
I see "MQBinding" in the exception list but you say you are using
"WSMQClient 5.3"???

How are you connecting to the queue manager?

You can only connect in binding mode if your Java code is running on the
same box as the queue manager. If so, see page 12 of the latest WMQ
Using Java manual. You are probably missing the environment variable:
LD_LIBRARY_PATH=/opt/mqm/java/lib

When connecting in client mode you MUST specify the following 3
fields:MQEnvironment.hostname = "server_hostname"; MQEnvironment.channel
= "SYSTEM.DEF.SVRCONN"; MQEnvironment.port = 1414;

If all else fails, RTFM. In particular, chapter 2 of WMQ Using Java.

later Roger...

Pepe

unread,
Jun 19, 2003, 5:41:26 PM6/19/03
to
1) The LD_LIBRARY_PATH variable is set to "/opt/mqm/java/lib"
2) I could not found a file named "mqjbnd05" or similar in
/opt/mqm/java/lib or in other F. place
3) I have RTFM, maybe I missed something...

PS: I'm using Linux as Client and want to connect it to a win2000 with
MQSeries Server 5.1. All using JMS API

thanks

RogerLacroix

unread,
Jun 20, 2003, 2:51:21 AM6/20/03
to
If you are connecting in client mode, what did you specify for
MQEnvironment.hostname, MQEnvironment.channel and MQEnvironment.port ??

Also, did you have an older version of WMQ previously installed
on the box?

later Roger...

Pepe

unread,
Jun 20, 2003, 10:32:33 AM6/20/03
to
MQEnvironment.hostname=win2000_server_ip
MQEnvironment.channel=my_channel_name MQEnvironment.port=1415 //server
listen in this port

No I don't have a previous version in Linux, but I'm trying to connect
MQClient 5.3 to MQSeries 5.1 may there reside the F. problem.

thanks.

PS:I'm RTFM again...

Pepe

unread,
Jun 20, 2003, 10:52:58 AM6/20/03
to
Now I'm using the method:

setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP); // Client mode

the sample run without problems, seems that as default the transport
type was JMSC.MQJMS_TP_BINDINGS_MQ // Bindings mode


I found this solution in page 193 of the F.M. ;)

thank Roger for your support. Greetings. Pepe-

0 new messages