AnsweredAssumed Answered

Recording IBM WebSphere MQ -- Missing required IBM JMS jar files

Question asked by jeff.wallace on Jan 15, 2016
Latest reply on Jan 21, 2016 by Kevin.Bowman

Like • Show 0 Likes0
Comment • 11

I'm attempting to do this with ::

CA DevTest 9.0

IBM WebSphere MQ Runtine 8.0.0

I'm trying to figure out how to create a virtual service by recording transactions to/from IBM WebSphere MQ. When I select the "IBM MQ Series (Deprecated)" transport protocol as defined in the official instructions, I get the following error.

I found this very similar discussion in the community and followed the advice of MarcyNunns

I went to my MQ installation {MQ_HOME/java/lib} and copied all of the JAR files and moved them into my DevTest CLASSPATH {LISA_HOME/lib}. (Initially, I only copy/pasted the JARs defined in that screenshot, but my MQ installation doesn't have the com.ibm.mqbind.jar or the dhbcore.jar)

However, even after copying all of the JARs into my LISA_HOME/lib and restarting the Workstation, I still get the exact same error.

Here are all of the JARs that I do have in my MQ installation ::

com.ibm.mq.allclient.jar

com.ibm.mq.axis2.jar

com.ibm.mq.commonservices.jar

com.ibm.mq.defaultconfig.jar

com.ibm.mq.headers.jar

com.ibm.mq.jar

com.ibm.mq.jmqi.jar

com.ibm.mq.jms.Nojndi.jar

com.ibm.mq.pcf.jar

com.ibm.mq.postcard.jar

com.ibm.mq.soap.jar

com.ibm.mq.tools.ras.jar

com.ibm.mq.traceControl.jar

com.ibm.mqjms.jar

fscontext.jar

jms.jar

jta.jar

libmqjbnd.so

libmqjexitstub02.so

providerutil.jar

Anybody have any ideas on exactly what JARs I need and where I can find them?

Thanks,

Jeff

No one else has this question

Outcomes

Kevin.Bowman

Jan 15, 2016 8:13 AM

It's not that you're missing jars. Some of the v8.0 IBM MQ classes depend on the newer JMS 2.0 API jar. To use the old MQ step with 8.0 MQ jars you will need javax.jms-api-2.0.jar, which can be downloaded here:

Maven Repository: javax.jms » javax.jms-api » 2.0

Place it in lib/ along with the MQ jars. This does not appear to cause problems with the rest of DevTest, but I have not done thorough testing on it yet.

Alternatively, the new IBM MQ Native VSE protocol does not try to load JMS classes, not even used by Native mode, in order to verify the right jars are present. If you're using IBM MQ Native mode then I would recommend using that protocol instead of the deprecated IBM MQ Series. Or, if you actually are using IBM MQ JMS mode then I'd recommend using the new JMS protocol, which does support IBM MQ JMS Mode.

Actions

jeff.wallace @ Kevin.Bowman on Jan 15, 2016 9:47 PM

Kevin -

Thank you for the reply.

I'm honestly not sure how to check what mode MQ is running in (still trying to figure that out)

I went ahead and tried using the "IBM MQ Native" Transport Protocol.

When I do that, I get a "NoClassDefFoundError: com/ibm/mq/MQ/MQException" error.

I also tried using the "JMS" Transport Protocol.

When I do that, I get a "Missing jar file com.ibm.mqjms.jar, usually found in IBMMQ_HOME/java/lib" error, but I do have that JAR sitting in my {LISA_HOME}/lib.

Any idea what else may be occurring?

Actions

Kevin.Bowman

@ jeff.wallace on Jan 15, 2016 10:30 PM

For your first error, com.ibm.mq.MQException can be found in com.ibm.mq.jmqi.jar. If this jar is present then look in your workstation log for another error above the NoClassFoundError. Some other problem is preventing it from loading the MQException class.

For your second error, this is still because you're missing javax.jms-api-2.0.jar. You cannot use IBM MQ JMS mode without that jar present.

Actions

jeff.wallace @ Kevin.Bowman on Jan 15, 2016 11:19 PM

Kevin -

The com.ibm.mq.jmqi.jar is present in the /lib dir.

The preceeding error message is :: "Value for Unknown Response Operation was null".

I'll attach the stacktrace from the Workstation log as a text file, since it's kind of long.

Thanks again for the assistance!

-Jeff

Attachments

Error.txt.zip1.8 KB

Actions

Kevin.Bowman

@ jeff.wallace on Jan 16, 2016 12:33 AM

That's an unrelated error. I'm sorry, but you're just going to have to get in touch with support and send us your whole log.

Are you running on a Mac by chance? Last I checked, the Mac launcher does not automatically pull everything from lib/, but it's been a very long time since I checked.

Actions

jeff.wallace @ Kevin.Bowman on Jan 19, 2016 3:37 PM

Kevin -

Nope, not running on a Mac. Using 64-bit Win7 Enterprise edition.

-Jeff

Actions

Kevin.Bowman

@ jeff.wallace on Jan 19, 2016 4:45 PM

I'm able to get the IBM MQ Native step to work with just the following v8.0.0.2 IBM MQ jars:

com.ibm.mq.commonservices.jar

com.ibm.mq.headers.jar

com.ibm.mq.jar

com.ibm.mq.jmqi.jar

com.ibm.mq.pcf.jar

com.ibm.mqjms.jar

dhbcore.jar

Can you check the exact version of your MQ jars? Open one of the .jar files like a .zip file, open META-INF/MANIFEST.MF with a text editor, and find the 'Implementation-Version' line.

Have you added any other, non MQ-related jars to lib/?

Actions

jeff.wallace @ Kevin.Bowman on Jan 19, 2016 10:36 PM

Here are the versions I get for those JARs ::

com.ibm.mq.commonservices.jar = Implementation-Version: p800-004-151017

com.ibm.mq.headers.jar = Implementation-Version: 8.0.0.4 - p800-004-151017

com.ibm.mq.jar = Implementation-Version: 8.0.0.4 - p800-004-151017

com.ibm.mq.jmqi.jar = Implementation-Version: 8.0.0.4 - p800-004-151017

com.ibm.mq.pcf.jar = Implementation-Version: 8.0.0.4 - p800-004-151017

com.ibm.mqjms.jar = Implementation-Version: 8.0.0.4 - p800-004-151017

dhbcore.jar = Implementation-Version: DH000-L50920

I haven't added any other JARs of any kind.

Actions

Kevin.Bowman

@ jeff.wallace on Jan 20, 2016 12:55 AM

Well, I got nothing.

Can you contact CA/DevTest support and get us your full workstation log? Mention that you've already talked to me on the forums and they can probably expedite things a bit. I'll probably also ask for you to send us your v8.0.0.4 so I can try them myself.

Actions

jeff.wallace @ Kevin.Bowman on Jan 21, 2016 8:35 PM

Thanks for all of the help Kevin. I ended up opening a ticket with support and got some more assistance. I believe that I have the proper set of JARs now for my setup.

com.ibm.mq.allclient.jar

com.ibm.mq.commonservices.jar

com.ibm.mq.headers.jar

com.ibm.mq.jar

com.ibm.mq.jmqi.jar

com.ibm.mq.pcf.jar

com.ibm.mqjms.jar

NOTE::I originally placed all of my JARs into a subfolder in lib (i.e. /lib/ibm/) and apparently you can't do that.

Now I just need to work with my MQ admins to setup proxy queues and identify if we also need to setup live queues.

Thanks again for all your help.

Actions

Kevin.Bowman

@ jeff.wallace on Jan 21, 2016 8:50 PM

NOTE::I originally placed all of my JARs into a subfolder in lib (i.e. /lib/ibm/) and apparently you can't do that.

Well there's your problem.

Now I just need to work with my MQ admins to setup proxy queues and identify if we also need to setup live queues.

Typically the "Live" queues are the ones your application runs on normally, and the service side of your application continues to operate on those queues. The proxy queues are created to insert the VSE recorder, and the client side of your application is reconfigured to use those queues.

Actions

11 Replies

Kevin.Bowman Jan 15, 2016 8:13 AM
Mark Correct
Correct Answer
It's not that you're missing jars. Some of the v8.0 IBM MQ classes depend on the newer JMS 2.0 API jar. To use the old MQ step with 8.0 MQ jars you will need javax.jms-api-2.0.jar, which can be downloaded here:

Maven Repository: javax.jms » javax.jms-api » 2.0

Place it in lib/ along with the MQ jars. This does not appear to cause problems with the rest of DevTest, but I have not done thorough testing on it yet.

Alternatively, the new IBM MQ Native VSE protocol does not try to load JMS classes, not even used by Native mode, in order to verify the right jars are present. If you're using IBM MQ Native mode then I would recommend using that protocol instead of the deprecated IBM MQ Series. Or, if you actually are using IBM MQ JMS mode then I'd recommend using the new JMS protocol, which does support IBM MQ JMS Mode.
Like • Show 0 Likes0
Actions
- jeff.wallace @ Kevin.Bowman on Jan 15, 2016 9:47 PM
  Mark Correct
  Correct Answer
  Kevin -
  
  Thank you for the reply.
  
  I'm honestly not sure how to check what mode MQ is running in (still trying to figure that out)
  
  I went ahead and tried using the "IBM MQ Native" Transport Protocol.
  When I do that, I get a "NoClassDefFoundError: com/ibm/mq/MQ/MQException" error.
  
  I also tried using the "JMS" Transport Protocol.
  When I do that, I get a "Missing jar file com.ibm.mqjms.jar, usually found in IBMMQ_HOME/java/lib" error, but I do have that JAR sitting in my {LISA_HOME}/lib.
  
  Any idea what else may be occurring?
  Like • Show 0 Likes0
  Actions
  - Kevin.Bowman @ jeff.wallace on Jan 15, 2016 10:30 PM
    Mark Correct
    Correct Answer
    For your first error, com.ibm.mq.MQException can be found in com.ibm.mq.jmqi.jar. If this jar is present then look in your workstation log for another error above the NoClassFoundError. Some other problem is preventing it from loading the MQException class.
    
    For your second error, this is still because you're missing javax.jms-api-2.0.jar. You cannot use IBM MQ JMS mode without that jar present.
    Like • Show 0 Likes0
    Actions
    - jeff.wallace @ Kevin.Bowman on Jan 15, 2016 11:19 PM
      Mark Correct
      Correct Answer
      Kevin -
      
      The com.ibm.mq.jmqi.jar is present in the /lib dir.
      
      The preceeding error message is :: "Value for Unknown Response Operation was null".
      
      I'll attach the stacktrace from the Workstation log as a text file, since it's kind of long.
      
      Thanks again for the assistance!
      
      -Jeff
      Attachments
      Error.txt.zip1.8 KB
      Like • Show 0 Likes0
      Actions
      - Kevin.Bowman @ jeff.wallace on Jan 16, 2016 12:33 AM
        Mark Correct
        Correct Answer
        That's an unrelated error. I'm sorry, but you're just going to have to get in touch with support and send us your whole log.
        
        Are you running on a Mac by chance? Last I checked, the Mac launcher does not automatically pull everything from lib/, but it's been a very long time since I checked.
        Like • Show 0 Likes0
        Actions
        jeff.wallace @ Kevin.Bowman on Jan 19, 2016 3:37 PM
        Mark Correct
        Correct Answer
        Kevin -
        
        Nope, not running on a Mac. Using 64-bit Win7 Enterprise edition.
        
        -Jeff
        Like • Show 0 Likes0
        Actions
        Kevin.Bowman @ jeff.wallace on Jan 19, 2016 4:45 PM
        Mark Correct
        Correct Answer
        I'm able to get the IBM MQ Native step to work with just the following v8.0.0.2 IBM MQ jars:
        
        com.ibm.mq.commonservices.jar
        com.ibm.mq.headers.jar
        com.ibm.mq.jar
        com.ibm.mq.jmqi.jar
        com.ibm.mq.pcf.jar
        com.ibm.mqjms.jar
        dhbcore.jar
        
        Can you check the exact version of your MQ jars? Open one of the .jar files like a .zip file, open META-INF/MANIFEST.MF with a text editor, and find the 'Implementation-Version' line.
        
        Have you added any other, non MQ-related jars to lib/?
        Like • Show 0 Likes0
        Actions
        jeff.wallace @ Kevin.Bowman on Jan 19, 2016 10:36 PM
        Mark Correct
        Correct Answer
        Here are the versions I get for those JARs ::
        
        com.ibm.mq.commonservices.jar      = Implementation-Version: p800-004-151017
        com.ibm.mq.headers.jar                  = Implementation-Version: 8.0.0.4 - p800-004-151017
        com.ibm.mq.jar                              = Implementation-Version: 8.0.0.4 - p800-004-151017
        com.ibm.mq.jmqi.jar                       = Implementation-Version: 8.0.0.4 - p800-004-151017
        com.ibm.mq.pcf.jar                         = Implementation-Version: 8.0.0.4 - p800-004-151017
        com.ibm.mqjms.jar                         = Implementation-Version: 8.0.0.4 - p800-004-151017
        dhbcore.jar                                     = Implementation-Version: DH000-L50920
        
        I haven't added any other JARs of any kind.
        Like • Show 0 Likes0
        Actions
        Kevin.Bowman @ jeff.wallace on Jan 20, 2016 12:55 AM
        Mark Correct
        Correct Answer
        Well, I got nothing.
        
        Can you contact CA/DevTest support and get us your full workstation log? Mention that you've already talked to me on the forums and they can probably expedite things a bit. I'll probably also ask for you to send us your v8.0.0.4 so I can try them myself.
        Like • Show 0 Likes0
        Actions
        jeff.wallace @ Kevin.Bowman on Jan 21, 2016 8:35 PM
        Mark Correct
        Correct Answer
        Thanks for all of the help Kevin. I ended up opening a ticket with support and got some more assistance. I believe that I have the proper set of JARs now for my setup.
        
        com.ibm.mq.allclient.jar
        com.ibm.mq.commonservices.jar
        com.ibm.mq.headers.jar
        com.ibm.mq.jar
        com.ibm.mq.jmqi.jar
        com.ibm.mq.pcf.jar
        com.ibm.mqjms.jar
        
        NOTE::I originally placed all of my JARs into a subfolder in lib (i.e. /lib/ibm/) and apparently you can't do that.
        
        Now I just need to work with my MQ admins to setup proxy queues and identify if we also need to setup live queues.
        
        Thanks again for all your help.
        Like • Show 0 Likes0
        Actions
        Kevin.Bowman @ jeff.wallace on Jan 21, 2016 8:50 PM
        Mark Correct
        Correct Answer
        NOTE::I originally placed all of my JARs into a subfolder in lib (i.e. /lib/ibm/) and apparently you can't do that.
        Well there's your problem.
        
        Now I just need to work with my MQ admins to setup proxy queues and identify if we also need to setup live queues.
        Typically the "Live" queues are the ones your application runs on normally, and the service side of your application continues to operate on those queues. The proxy queues are created to insert the VSE recorder, and the client side of your application is reconfigured to use those queues.
        Like • Show 1 Like1
        Actions

Recording IBM WebSphere MQ -- Missing required IBM JMS jar files

Outcomes

Attachments

Related Content

Recommended Content

Incoming Links