MQJE001: Completion Code 2, Reason 2035, different behaviour - Websphere

This is a discussion on MQJE001: Completion Code 2, Reason 2035, different behaviour - Websphere ; Hi, I'm migrating a J2EE application from weblogic 7.0 to weblogic 10.0 on WINDOWS OS with IBM MQ as the middleware layer. The code behaves works perfectly fine on Weblogic7.0-UNIX but fails on Weblogic-10-NT with the following error. The MQConnectionFactory ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: MQJE001: Completion Code 2, Reason 2035, different behaviour

  1. MQJE001: Completion Code 2, Reason 2035, different behaviour

    Hi,



    I'm migrating a J2EE application from weblogic 7.0 to weblogic 10.0 on WINDOWS OS with IBM MQ as the middleware layer. The code behaves works perfectly fine on Weblogic7.0-UNIX but fails on Weblogic-10-NT with the following error.



    The MQConnectionFactory is created at run-time and bound to weblogic using jndi.


    //Added after the code failed

    initialCtxProperties.setProperty( Context.SECURITY_AUTHENTICATION, "none");



    Code failure

    .......

    qReceiver = qSession.createReceiver( queue);





    com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2035

    at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManag er.java:2858)

    at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManag er.java:2915)

    at com.ibm.mq.jms.MQSession.createQReceiver(MQSession .java:5581)

    at com.ibm.mq.jms.MQQueueSession.createReceiver(MQQue ueSession.java:276)



    at com.ibm.mq.jms.MQQueueSession.createReceiver(MQQue ueSession.java:254)



    MQ client libraries : version 6.0.



    My administrators tell me that it is an issue with authenication. But I'm puzzled why the code works perfectly fine on weblogic70-Unix with no SECURITY_AUTHENTICATION set and why is that the authentication is requested from Weblogic 10.0



    Any help greatly appreciated.



    thanks

    Ajit

  2. Re: MQJE001: Completion Code 2, Reason 2035, different behaviour

    2035 - MQRC_NOT_AUTHORIZED



    In the mentioned scenario, check whether the Windows-NT user is authorized to access MQ, using which you have started Weblogic-10-NT server. If the user is not authorized, then you will have to add the NT-User id to the MQM group, or give authentication to a NT-User id for a specific queue.

+ Reply to Thread