The Integration Zone is brought to you in partnership with CA Technologies. Download their eBook to learn more about API Strategy and Architecture.
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
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
Now, run your client again, and the error should go away. HTH.
The Integration Zone is brought to you in partnership with CA Technologies. Use this model to create a sustainable API strategy that will help your organization adapt and succeed in the app economy.
Published at DZone with permission of
, DZone MVB
Opinions expressed by DZone contributors are their own.