| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Another issue with MQ Explorer v6 |
« View previous topic :: View next topic » |
| Author |
Message
|
| RogerLacroix |
 Posted: Wed Mar 14, 2007 10:56 am Post subject: Another issue with MQ Explorer v6 |
 |
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
All,
In case you didn't know, client-side security exits do not work with MQ Explorer v6.0.0. But do work with MQ Explorer v6.0.1.
I have recently had a customer on Windows upgrade from WMQ v6.0.1.0 to WMQ v6.0.2.0 and now client-side security exits do not work.
I did a bunch of testing with both MQ Explorer v6.0.1 and v6.0.2 to see what the issue is.
The problem seems to be related to either a path or classpath issue.
Client-side security exit are not directly supported by MQ Explorer v6, you must use a client channel table (it is very complex indirect method).
To add a remote queue manager in MQ Explorer v6, you give the name and then point to the client channel table.
But when you click 'Finish', a popup window appears (connecting to...) along with the Windows hourglass. The process never ends for v6.0.2. What has happened is MQ has thrown an exception about not finding the 'com.ibm.mq.MQSecurityExit' but it was not caught by the code. Hence, the indefinite wait - hourglass.
To verify it, Eclipse should have created a log file called: '.log' and it is located at (it may be a hidden file):
%USERPROFILE%\Application Data\IBM\MQ Explorer\.metadata\.log
And the contains will look like:
| Code: |
!ENTRY org.eclipse.ui 4 0 Mar 13, 2007 21:36:09.78
!MESSAGE com.ibm.mq.MQSecurityExit
!STACK 0
java.lang.NoClassDefFoundError: com.ibm.mq.MQSecurityExit
at java.lang.ClassLoader.defineClassImpl(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:211) |
I checked all paths, classpaths and the default queue manager 'Exit Directory' and everything looks normal.
So, I guessed that there must be a bug / problem with the new MQ Java runtime.
When you upgrade from 6.0.0 to 6.0.1 to 6.0.2, the installer does not delete the old MQ JAR files, so I copied the MQ JAR files from:
<MQ_Install_Path>\eclipse\plugins\com.ibm.mq.runtime_6.0.1.0\lib
to
<MQ_Install_Path>\eclipse\plugins\com.ibm.mq.runtime_6.0.2.0\lib
And voila, everything works (make sure you backup your MQ JAR files).
Actually, I believe you only need to copy over the 'com.ibm.mq.jar' MQ JAR file. I just haven't had a chance to test it.
I have asked the customer to open a PMR with IBM to get this issue fixed.
In this day and age of security, security, security - I really don't understand how an IBM product manager would allow / approve removing direct support of client-side security exit from MQ Explorer v6. In earlier releases on MQ Explorer (i.e. v5.*), it was directly supported and very easy to implement.
Well at least products like MO71, WBIMB ToolKit, WMQTool, etc... understand the need for security and directly support client-side security exits.
Does anyone know who is actually responsible for MQ Explorer v6 features / functionality? Because I have real customers who would like to express their requirements for MQ Explorer v6 to directly support client-side security exits.
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
 |
| kevinf2349 |
| Posted: Wed Mar 14, 2007 11:50 am Post subject: |
|
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
Roger.
Check your PM's
Kevin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
