IBM fixed a quirk in MQ

Wow, IBM fixed a quirk in IBM MQ for Windows and I never in noticed until now. 🙂

3 and 1/2 years ago, I wrote a blog posting here about Java applications connecting in ‘bindings mode’ and receiving Reason Code of 2495 when using 64-bit JVM on Windows. You can read the blog posting for the ‘who, what, where, when and why’.

So, today I wanted to do some testing with MQ Visual Edit and a 64-bit JVM on Windows. I wanted to see if I could come up with a work around to the problem. I ran it and everything worked. My first reaction was that I have the fix in the batch file. I checked – nothing then I thought, I have the java\lib and java\lib64 flipped in the PATH environment variable. I checked – no, the 32-bit one is first.

I scratched my head and starting testing MQ Visual Edit with IBM MQ JAR files from earlier releases and it appears that in IBM MQ v7.5.0.2 the quirk was fixed. The earliest MQ v7.5 JAR files where it worked is v7.5.0.2. When I try MQ JAR files from v7.5.0.0, it fails. (I don’t have MQ JAR files from v7.5.0.1.)

Note: I did MQ Visual Edit 64-bit JVM testing with various MQ JAR files from v8.0 and v9.0 and they all work perfectly.

So, I’m happy to see this quirk being fixed. 🙂

Regards,
Roger Lacroix
Capitalware Inc.

This entry was posted in Java, JMS, MQ, Windows.

One Response to IBM fixed a quirk in MQ

  1. JoshMc says:

    IC90089: WEBSPHERE MQ JAVA CLASSES FOR WINDOWS RUNNING IN A 64-BIT JVM ARE UNABLE TO CONNECT TO A QUEUE MANAGER IN BINDINGS MODE