Capitalware would like to announce that NetFlexity is a Silver Sponsor of MQ Technical Conference v2.0.1.7 (MQTC).
For more information, please go to: http://www.mqtechconference.com
Regards,
Roger Lacroix
Capitalware Inc.
Capitalware would like to announce that NetFlexity is a Silver Sponsor of MQ Technical Conference v2.0.1.7 (MQTC).
For more information, please go to: http://www.mqtechconference.com
Regards,
Roger Lacroix
Capitalware Inc.
David Richards of IBM will be speaking at MQ Technical Conference v2.0.1.7 (MQTC).
For more information about MQTC, please go to:
http://www.mqtechconference.com
Regards,
Roger Lacroix
Capitalware Inc.
It is always interesting to see what IBM Support thinks of issues and their resolution. 🙂
Case in point: https://developer.ibm.com/messaging/2017/08/01/using-channel-exits-jee-application-servers/
Background: Several months ago, a long-time customer of MQ Authenticate User Security Exit (MQAUSX) was deploying a JBoss V7 server and needed to configure the MQAUSX client-side security exit to be used for authentication to the queue manager where the MQAUSX server-side security exit is located.
I had the customer follow the standard JEE method of updating the CLASSPATH but MQ complained that the client-side security exit could not be found. For days and days, we tried every combination of CLASSPATH, PATH, etc that I could think to get MQ to find the MQAUSXJ.jar file. But it always failed.
The thing that was becoming very clear, when a JEE application uses the MQ Resource Adapter (aka wmq.jmsra.rar), the environment becomes a closed system for MQ related items. I got the bright idea of hacking the MQ Resource Adapter and putting the MQAUSXJ.jar inside it then re-bundling the MQ Resource Adapter. The customer deployed the ‘new and improved’ MQ Resource Adapter and everything worked. 🙂
The only problem, the customer did not liked the idea of hacking the MQ Resource Adapter and inserting the MQAUSXJ.jar file into it. So they opened a PMR with IBM.
As noted in the IBM blog posting, IBM Support came up with 3 solutions. The only viable solution was the first option of setting the JVM environment variable of com.ibm.mq.cfg.ClientExitPath.JavaExitsClasspath.
i.e. Windows
com.ibm.mq.cfg.ClientExitPath.JavaExitsClasspath=C:/Capitalware/MQAUSX/MQAUSXJ.jar
i.e. Unix/Linux
com.ibm.mq.cfg.ClientExitPath.JavaExitsClasspath=/var/mqm/exits64/MQAUSXJ.jar
I have updated the MQAUSX manual to reflect this information.
IBM Support’s description of the 2nd customer isn’t exactly correct (they were using both send and receive exits). This customer was using WAS (WebSphere Application Server) with the MQ Resource Adapter and wanted to use MQ Channel Encryption (MQCE) for both send and receive exits.
At first, my brain did not connect the JBoss V7 channel security exit issues with this new issue of WAS channel send and receive exits not working. I didn’t make the connection that both customers were using the MQ Resource Adapter. So, the customer opened a PMR with IBM and basically received the same response as the other customer received and then the bells went off in my head. (MQ Resource Adapter is a closed system as it relates to MQ items.)
I have updated the MQCE manual to reflect this information.
i.e. Windows
com.ibm.mq.cfg.ClientExitPath.JavaExitsClasspath=C:/Capitalware/MQCE/MQCEJ.jar
i.e. Unix/Linux
com.ibm.mq.cfg.ClientExitPath.JavaExitsClasspath=/var/mqm/exits64/MQCEJ.jar
So, here’s the bottom-line: if you use the MQ Resource Adapter (aka wmq.jmsra.rar) in your JEE application and want to also use MQ exits then you need to add the JVM environment variable of com.ibm.mq.cfg.ClientExitPath.JavaExitsClasspath with the path and filename of the JAR file that contains the classes for the MQ exits.
Regards,
Roger Lacroix
Capitalware Inc.
Lyn Elkins of IBM is allowing Robin Wiley to load his DataPower Labs onto the computers in the MQ Labs at MQ Technical Conference v2.0.1.7 (MQTC).
So attendees will be able to not only attend Robin Wiley’s ‘MQ-DataPower Connectivity Deep Dive’ session but also run through the DataPower Labs he has.
For more information about MQTC, please go to:
http://www.mqtechconference.com
Regards,
Roger Lacroix
Capitalware Inc.
Capitalware Inc. would like to announce the official release of MQ Visual Edit v2.2.0. This is a FREE upgrade for ALL licensed users of MQ Visual Edit V2. MQ Visual Edit allows users to view, manipulate and manage messages in a queue and/or topic of a IBM MQ queue manager and presents the data in a simplified format similar to a database utility or spreadsheet program.
For more information about MQ Visual Edit go to:
https://www.capitalware.com/mqve_overview.html
Regards,
Roger Lacroix
Capitalware Inc.
Capitalware Inc. would like to announce the official release of MQ Visual Browse v2.2.0. This is a FREE upgrade for ALL licensed users of MQ Visual Browse V2. MQ Visual Browse allows users to view messages in a queue and/or topic of a IBM MQ queue manager and presents the data in a simplified format similar to a database utility or spreadsheet program.
For more information about MQ Visual Browse go to:
https://www.capitalware.com/mqvb_overview.html
Regards,
Roger Lacroix
Capitalware Inc.
Here’s a good write up by Colin Paice on issues and handling of them when your queue manager won’t shutdown.
https://developer.ibm.com/messaging/2017/07/28/isnt-queue-manager-shutting/
Regards,
Roger Lacroix
Capitalware Inc.
The following applies to Capitalware Java products and any other program that uses Java (JVM) on Windows 10 with a recent Creators Update. Microsoft has changed something in Windows 10 that causes Java (JVM) to crash for some users (not all) when accessing a file.
For those IBM MQ users, just to refresh your memory, the following are MQ Java programs: MQ Explorer, JMSAdmin, Postcard, IVT (Verification), MQTT Listener, AMQP Listener, Java and Java/JMS sample applications, etc..
If you are using a Java program on Windows 10 that requires Java (JVM) and you get EXCEPTION_ACCESS_VIOLATION with [MSVCR100.dll+0x121f4] then you may have the issue.
Microsoft has it documented here: Creators Update causing Java crashes
This issue appears to happen with most JVM’s. i.e. Oracle JRE, Excelsior Jet, OpenJDK, etc.. I cannot find a report of it with IBM JRE but it mostly likely has the issue too.
Capitalware’s Java products are desktop GUI programs, so if you see a popup box like the following then you have been hit with the issue:
Solution? Yes, sir, there is a solution and it is even stranger than the issue. It is a very simple solution: create a GodMode folder on your desktop and the issue goes away. I’m not kidding. Don’t ask me how many backdoors there are in Windows!!!
Here is a write up of the solution: Create a ‘God Mode’ Folder in Windows 10.
GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}
If you scroll further down on the GodMode link, you will see a comment that the word ‘GodMode’ can be anything (i.e. BudaMode, YahwahMode, etc..).
So there you go, when dealing with Windows, you just have entered the Twilight Zone. 🙂
Regards,
Roger Lacroix
Capitalware Inc.
Rob Sordillo of Avada Software will be doing the following vendor session at MQ Technical Conference v2.0.1.7 (MQTC):
For more information about MQTC, please go to:
http://www.mqtechconference.com
Regards,
Roger Lacroix
Capitalware Inc.
Capitalware would like to announce that TxMQ is a Gold Sponsor of MQ Technical Conference v2.0.1.7 (MQTC).
For more information, please go to: http://www.mqtechconference.com
Regards,
Roger Lacroix
Capitalware Inc.