2 Replies Latest reply: Dec 18, 2012 6:30 AM by 980549 RSS

    Sonic MQ to Oracle Enterprise Gateway Integration [OEG]

    961360
      Hi

      I am trying to configure policies in OEG to read messages from a Sonic MQ queue. I found a whitepaper in oracle.com but the instructions do not seem to be quite explanatory for a new user/developer.

      As per the instructions, after much struggle, I had created the JNDI entries in Sonic MQ and finished configuring a new JMS Service, JMS Session, policies, etc in the Policy Studio / OEG Dashboard. But while trying to deploy the configured artefacts in the policy studio, I am getting the following error. Please help in resolving the following error.

      ERROR 2012/09/11 15:45:26.953 cannot reconfigure module type JMSService: unloading the entity:{name=SonicMQ}:
      com.vordel.es.EntityStoreException: cannot configure JMS Service
           at com.vordel.dwe.jms.JMSService.configure(JMSService.java:171)
           at com.vordel.dwe.jms.JMSServiceGroup.configure(JMSServiceGroup.java:34)
           at com.vordel.dwe.Service.refresh(Service.java:430)
           at com.vordel.pd.agent.ManagementAgentImpl.deployImpl(ManagementAgentImpl.java:296)
           at com.vordel.pd.agent.ManagementAgentImpl.deploy(ManagementAgentImpl.java:136)
           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
           at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
           at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
           at java.lang.reflect.Method.invoke(Method.java:597)
           at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:388)
           at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:283)
           at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:319)
           at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
           at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
           at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
           at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453)
           at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
           at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
           at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
           at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
           at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
      Caused by: javax.naming.AuthenticationException: Failed to connect to the management broker due to authentication failure; connection state=1
           at com.sonicsw.jndi.mfcontext.MFConnectionManager.connect(MFConnectionManager.java:109)
           at com.sonicsw.jndi.mfcontext.MFConnectionManager.<init>(MFConnectionManager.java:79)
           at com.sonicsw.jndi.mfcontext.MFConnectionManager.getManager(MFConnectionManager.java:41)
           at com.sonicsw.jndi.mfcontext.MFContext.<init>(MFContext.java:141)
           at com.sonicsw.jndi.mfcontext.MFContextFactory.getInitialContext(MFContextFactory.java:51)
           at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
           at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
           at javax.naming.InitialContext.init(InitialContext.java:223)
           at javax.naming.InitialContext.<init>(InitialContext.java:197)
           at com.vordel.dwe.jms.JMSService.configure(JMSService.java:144)
           ... 20 more


      ERROR 2012/09/11 15:45:26.969 Failed to replace original conf: Failed to configure module: '/[NetService]name=Service/[JMSSession]name=Id-0001347357709842-0000000006fb7b3e-1' reason: 'Couldn't locate JMSService for session: <key type='JMSServiceGroup'><id field='name' value='JMS Services'/><key type='JMSService'><id field='name' value='SonicMQ'/></key></key>':
      com.vordel.es.EntityStoreException: Failed to configure module: '/[NetService]name=Service/[JMSSession]name=Id-0001347357709842-0000000006fb7b3e-1' reason: 'Couldn't locate JMSService for session: <key type='JMSServiceGroup'><id field='name' value='JMS Services'/><key type='JMSService'><id field='name' value='SonicMQ'/></key></key>'
           at com.vordel.dwe.Service.throwit(Service.java:446)
           at com.vordel.dwe.Service.refresh(Service.java:432)
           at com.vordel.pd.agent.ManagementAgentImpl.deployImpl(ManagementAgentImpl.java:296)
           at com.vordel.pd.agent.ManagementAgentImpl.deploy(ManagementAgentImpl.java:136)
           at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
           at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
           at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
           at java.lang.reflect.Method.invoke(Method.java:597)
           at org.apache.axis.providers.java.RPCProvider.invokeMethod(RPCProvider.java:388)
           at org.apache.axis.providers.java.RPCProvider.processMessage(RPCProvider.java:283)
           at org.apache.axis.providers.java.JavaProvider.invoke(JavaProvider.java:319)
           at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
           at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
           at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
           at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java:453)
           at org.apache.axis.server.AxisServer.invoke(AxisServer.java:281)
           at org.apache.axis.transport.http.AxisServlet.doPost(AxisServlet.java:699)
           at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
           at org.apache.axis.transport.http.AxisServletBase.service(AxisServletBase.java:327)
           at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
      Caused by: com.vordel.es.EntityStoreException: Couldn't locate JMSService for session: <key type='JMSServiceGroup'><id field='name' value='JMS Services'/><key type='JMSService'><id field='name' value='SonicMQ'/></key></key>
           at com.vordel.dwe.jms.JMSSession.configure(JMSSession.java:42)
           at com.vordel.dwe.Service.refresh(Service.java:430)
           ... 18 more

      Thanks

      @np

      Edited by: user13168628 on Sep 11, 2012 5:35 AM
        • 1. Re: Sonic MQ to Oracle Enterprise Gateway Integration [OEG]
          961360
          Hello

          Can you guys please provide your valuable inputs and help me out?
          • 2. Re: Sonic MQ to Oracle Enterprise Gateway Integration [OEG]
            980549
            Hi,

            I just had the same error when configuring a JMS Service for an MQ 7.1 connection.

            I restarted the OEG instance and got an MQ authorization error:

            com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
            ...stack cut...
            com.vordel.es.EntityStoreException: cannot configure JMS Service
            ...stack cut...
            Caused by: com.ibm.msg.client.jms.DetailedJMSSecurityException: JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager 'xxxxxxxxxx' with connection mode 'Client' and host name 'xx.xx.xx.xx(1414)'. Please check if the supplied username and password are correct on the QueueManager you are connecting to
            ...stack cut...
            Caused by: com.ibm.mq.MQException: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
            at com.ibm.msg.client.wmq.common.internal.Reason.createException(Reason.java:223)
            ... 11 more


            Looking in the MQ logs I could see the channel was blocked:


            18/12/2012 14:11:29 - Process(2116.21) User(MUSR_MQADMIN) Program(amqrmppa.exe)
            Host(xxxxxxxxxx) Installation(Installation1)
            VRMF(7.1.0.1) QMgr(xxxxxxxxxx)

            AMQ9777: Channel was blocked


            I added a suitable Channel Authentication Record and restarted the gateway successfully.

            I could then deploy without errors.