MQ

MQ

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

  • 1.  RC 2278 -CLIENT_CONN_ERROR Using CCDT JSON with WAS 9.0.5.6 & MQ 9.2.0.3

    Posted Tue January 18, 2022 11:07 AM

    From the documentation in Knowledge Center, it implies that Websphere Application Server (WAS) doesn't handle CCDT file built with newer versions of MQ - using WAS built-in resource.  In my case it is WAS 9.0.5.6 with MQ 9.2.0.3.  However, although I was able to successfully build and tested a WAS QCF using the binary CCDT, the same QCF failed with RC 2278 -CLIENT_CONN_ERROR when I changed from a binary to json CCDT file.  I tried, as the documentation suggests and added the MQ java native library path {MQ_INSTALL_ROOT}\java\lib64 to the WAS MQ JMS provider (Windows OS) – hoping that this would fix the issue, but it didn't .  I can't find anything specific in the KC regarding any issues using a MQ json CCDT with WAS so I am wondering if someone can help me figure out how to resolve this issue. 

     

    Regards,

     

    Tony Thomas

    ​​​​​​​​

    ------------------------------
    Anthony Thomas
    ------------------------------


  • 2.  RE: RC 2278 -CLIENT_CONN_ERROR Using CCDT JSON with WAS 9.0.5.6 & MQ 9.2.0.3

    Posted Wed January 19, 2022 12:40 PM
    That's because your library path is wrong. It should be the class path and not the  java native library path. it should read
    {MQ_INSTALL_ROOT}\java\lib64;{MQ_INSTALL_ROOT}\java\lib​

    The relevant jar file you're looking for is in java/lib but if you have a 64 bit java you want the dlls and other relevant stuff to be picked up from java\lib64...
    You'll need to have both on your path in the order to make sure 64 stuff gets picked up first...



    ------------------------------
    Francois Brandelik
    ------------------------------

    Original Message


  • 3.  RE: RC 2278 -CLIENT_CONN_ERROR Using CCDT JSON with WAS 9.0.5.6 & MQ 9.2.0.3

    Posted Wed January 19, 2022 09:25 PM
    ​There is a "Update resource adapter" button under the box for the "Native library path".  Pressing that button allowed me to browse to the MQ installed resource adapter @ {MQ_INSTALL_ROOT}\java\lib\jca\WMQ.jmsra.rar and used it to update the WAS built-in RA.  I was then able to verify the QCF connection using the json CCDT.  The last screen before the actual update showed both the WAS built-in and the MQ 9.2.0.3 RA versions to allow you to compare and decide.
    ​

    ------------------------------
    Anthony Thomas
    ------------------------------

    Original Message


  • 4.  RE: RC 2278 -CLIENT_CONN_ERROR Using CCDT JSON with WAS 9.0.5.6 & MQ 9.2.0.3

    Posted Sat January 22, 2022 02:09 PM
    Hi Francois,

    Although I got it to work by upgrading WAS resource adapter with the one in the current version of MQ, I think adding the class path would be a more simpler solution. However, ​restoring the WAS built-in adapter and adding the class path in the order you suggested still didn't correct the problem (I added it in the "Native library path" box  in  "Resources ->  JMS -> JMS providers -> WebSphere MQ messaging provider" . Is there something that I still could be missing?  Where exactly in WAS do I need to put these two path - since I suspect I might be putting them in the wrong place?  I am really a MQ SME and is just familiar with WAS.

    Thanks in advance for your help.

    -Tony
    ​​

    ------------------------------
    Anthony Thomas
    ------------------------------

    Original Message


Related Content