0 Replies Latest reply on Dec 11, 2008 10:30 AM by Jurgen Van Bouchaute

    Issued when configuring JMS Listener & JMSRouter to use an W

    Jurgen Van Bouchaute Newbie

      Hi,

      we want to access with JBOSS ESB a WebSphere MQ6 provider by using a JMSListener and JSRouter.

      Both however get a authentication error when the listener and JMSrouter are instantiated :

      Caused by: org.jboss.soa.esb.helpers.NamingContextException: Failed to create Naming Context
      at org.jboss.soa.esb.helpers.NamingContextPool.createContext(NamingContextPool.java:365)
      at org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingContextPool.java:304)
      at org.jboss.soa.esb.helpers.NamingContextPool.getContext(NamingContextPool.java:159)
      at org.jboss.soa.esb.helpers.NamingContextPool.getNamingContext(NamingContextPool.java:410)
      at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.prepareMessageReceiver(JmsGatewayListener.java:375)
      at org.jboss.soa.esb.listeners.gateway.JmsGatewayListener.doInitialise(JmsGatewayListener.java:109)

      Caused by: javax.naming.ServiceUnavailableException: Unable to connect to the target queue manager xxxxxx-1:11451/AGM_GWT11.BT1 [Root exception is com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2035]
      at com.ibm.mq.jms.context.MQContext.(MQContext.java:196)
      at com.ibm.mq.jms.context.WMQInitialContextFactory.getInitialContext(WMQInitialContextFactory.java:29)
      at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
      at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)



      Caused by: com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2035
      at com.ibm.mq.MQQueueManager.accessQueue(MQQueueManager.java:2854)
      at com.ibm.mq.pcf.PCFAgent.open(PCFAgent.java:335)
      at com.ibm.mq.pcf.PCFAgent.open(PCFAgent.java:306)
      at com.ibm.mq.pcf.PCFAgent.connect(PCFAgent.java:240)
      at com.ibm.mq.pcf.PCFAgent.(PCFAgent.java:174)
      at com.ibm.mq.pcf.PCFMessageAgent.(PCFMessageAgent.java:146)
      at com.ibm.mq.jms.context.MQContext.(MQContext.java:183)





      When I use a third party JMS tool to access that provider/channel and queues , everything goes ok (using the same IBM MQ API libs).

      In the wiki article JBossESBMessagingSupport , the suggested solution is to define the user running the ESB server as part of the MQM group, but this is not allowed by policy.

      Any suggestions ?

      Thanks.

      Jurgen.