Service Virtualization

Expand all | Collapse all

Unable to publish / Subscribe message from IBM MQ

  • 1.  Unable to publish / Subscribe message from IBM MQ

    Posted Sep 17, 2018 09:19 PM

    I am getting the error "Error opening queue manager ****, Completion Code 2 (MQCC_FAILED), Reason Code 2035 (MQRC_NOT_AUTHORIZED)" while trying to publish / Subscribe message from IBM MQ.

     

    I am using DevTest 10.3, please suggest the resolution if anyone faced this issue.



  • 2.  Re: Unable to publish / Subscribe message from IBM MQ

    Broadcom Employee
    Posted Sep 18, 2018 08:27 AM

    You need to enter the correct username and password.  You may have to add these fields to the MQ Queue Manager Asset with the '+' button, they are located at 'Basic' -> 'User ID' and 'Basic' -> 'Password'.

     

    Refer to this link:

     

    IBM MQ and SSL/TLS 



  • 3.  Re: Unable to publish / Subscribe message from IBM MQ

    Posted Sep 18, 2018 07:20 PM

    Thanks Marcy for the response, but we don't need the Credentials to connect. We are able to connect from some other tool without auth details.



  • 4.  Re: Unable to publish / Subscribe message from IBM MQ



  • 5.  Re: Unable to publish / Subscribe message from IBM MQ

    Posted Sep 18, 2018 07:21 PM

    Thanks Prema, I will look into this.



  • 6.  Re: Unable to publish / Subscribe message from IBM MQ
    Best Answer

    Broadcom Employee
    Posted Sep 21, 2018 05:00 AM

    Hi Raghu

                  Yes, I have faced this issue. If you are connecting to IBM MQ via JMS, then make sure you add a JMS Connection object and provide user name and password in addition to a 'JMS Connection Factory' Object. Please see the screenshots below as to how I have defined them in my local env.

     

    JMS Connection Factory Object

     

    JMS Connection Object

    Please note that the JMS Connection object adds a reference to the JMS Connection Factory object that I have defined in previous step

     

    The screenshot below shows the queue definition. Here I use the JMS Connection object that was defined in previous step

     

     

    If you still face the 2035 error even after defining JMS connection and passing username and password, please check the following on the MQ Server side.

     

    Launch IBM Mq explorer, locate the queue manager that you have defined and check the steps shown below. Just delete the 'Block user' policy if it has been defined in the 'Channel Authentication Records'. If you still face the problem, lets have a webex session to go over this. You may reach me at natsa03@ca.com

     



  • 7.  Re: Unable to publish / Subscribe message from IBM MQ

    Posted Sep 24, 2018 12:49 AM

    Hi Sankar,

    Thanks for you response. 

    I tried your suggestion, Still no luck. For my case I don't need to pass credentials to connect to MQ Manager. We are able to connect to the same MQ manager from other tool without using userID & Password.



  • 8.  Re: Unable to publish / Subscribe message from IBM MQ

    Broadcom Employee
    Posted Sep 24, 2018 02:02 AM

    Hi Raghu

                     Please let me know your convenient time. I shall setup a webex session with you to go over this.

     

    regards

    Sankar



  • 9.  Re: Unable to publish / Subscribe message from IBM MQ

    Posted Sep 26, 2018 02:23 AM

    Hi Sankar,

     

    Using the MQ 7 jars with this approach(Using JMS SendReceive step) by leaving UserId and Password blank has resolved the issue, thanks heaps for your expert advise.



  • 10.  Re: Unable to publish / Subscribe message from IBM MQ

    Broadcom Employee
    Posted Sep 26, 2018 02:52 AM

    Super ! Thats a good news.

     

    -Sankar



  • 11.  Re: Unable to publish / Subscribe message from IBM MQ

    Broadcom Employee
    Posted Sep 25, 2018 11:17 AM

    Raghu,

     

    Open a new support case and we can get on a webex.

     

    ~Marcy



  • 12.  Re: Unable to publish / Subscribe message from IBM MQ

    Posted Sep 26, 2018 01:10 AM

    Thank you Marcy, I had raised a support ticket.