Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Solving the IBM MQ Client Error – No mqjbnd in java.library.path

DZone's Guide to

Solving the IBM MQ Client Error – No mqjbnd in java.library.path

· Integration Zone
Free Resource

Today’s data climate is fast-paced and it’s not slowing down. Here’s why your current integration solution is not enough. Brought to you in partnership with Liaison Technologies.

If you come across this issue when you try to connect a JMS client to IBM MQ (v7.0.x.x), this has nothing to do with any environment variables or VM arguments, at least it wasn’t for me (There are quite a lot of those articles out there, that makes you think this is the problem).

The fix for this will has to be done on the server side. Open the MQ Explorer. Now, if you have not done so already, you need to add your JNDI directory to JMS Administered Objects. In the Connection Factories,  you will note that your factories’ transport type is actually “Binding”. You need to right-click and go to the switch transport option which will have the “MQ Client” option that needs to be selected. Now the transport type will be “Client”. Do this to all Connection Factories that you are connecting to. Now, your configuration will look something like below:

Screen Shot 2013-03-20 at 5.28.49 PM

Now, run your client again, and the error should go away. HTH.

Is iPaaS solving the right problems? Not knowing the fundamental difference between iPaaS and iPaaS+ could cost you down the road. Brought to you in partnership with Liaison Technologies.

Topics:

Published at DZone with permission of Tharindu Mathew, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}