Netweaver 7.3 interoperate with Websphere MQ Error

former_member482483 · ‎11-16-2011

Hi,

I was having problem to make my MDB (MessageDrivenBean) to listen to Websphere Queue. I have created all jms resources accordingly, but still encountered exception : javax.jms.InvalidDestinationException: queue:///CRRS.BROKER.REQ.UPD.03.

-

#2.0 #2019 10 06 18:52:20:914#+0800#Warning#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000CA0000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Attempt to activate endpoint has failed. Attempt number 0#

#2.0 #2019 10 06 18:52:20:914#+0800#Error#com.sap.jms.resourceadapter.ResourceAdapterImpl#

com.sap.ASJ.jms.000002#BC-JAS-JMS#jms#C0007F00000101E2000000CC0000161C#22411250000000044##com.sap.jms.resourceadapter.ResourceAdapterImpl#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

There were problems initializing a Message-Driven Bean (MDB) of application sap.com/CRRSRatingEAR. No messages will be delivered to it. For more details, refer to the trace file.#

#2.0 #2019 10 06 18:52:20:915#+0800#Error#com.sap.jms.resourceadapter.ResourceAdapterImpl#

#BC-JAS-JMS#jms#C0007F00000101E2000000CD0000161C#22411250000000044##com.sap.jms.resourceadapter.ResourceAdapterImpl#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

ActivationSpec could not be deployed/started due to internal problem, clean up will be performed, the activation spec was applicationName=sap.com/CRRSRatingEAR,connectionFactoryName : QCF_1,mAcknowledgeMode : null,maxPoolSize : 50,mClientId : null,mDestinationName : CRRS.BROKER.REQ.UPD.03,mDestinationType : javax.jms.Queue,minPoolSize : 0,mMessageSelector : null,mSubscriptionDurability : null,mSubscriptionName : null,mSAPMDBFailoverActivation : FALSE,mReconnectAttempts : 30,mSleepBetweenAttempts : 5000,mParallelConsumers : 1

[EXCEPTION]

javax.resource.spi.UnavailableException: Could not activate endpoint for the configured number of attempts

at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:193)

at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:130)

at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:608)

at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findResourceAdapterByName(EndpointActivationImpl.java:156)

at com.sap.engine.services.connector.jca15.EndpointActivationImpl.findAdapter(EndpointActivationImpl.java:95)

at com.sap.engine.services.connector.jca15.EndpointActivationImpl.activateEndpoint(EndpointActivationImpl.java:68)

at com.sap.engine.services.ejb3.facades.internal.impl.server.MessagingFacadeImpl.activateEndpoint(MessagingFacadeImpl.java:43)

at com.sap.engine.services.ejb3.runtime.impl.Actions_MDBEndpointActivation.perform(Actions_MDBEndpointActivation.java:75)

at com.sap.engine.services.ejb3.container.CompositeAction.perform(CompositeAction.java:84)

at com.sap.engine.services.ejb3.container.ApplicationStarter.perform(ApplicationStarter.java:206)

at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl$Actions.perform(ContainerInterfaceImpl.java:912)

at com.sap.engine.services.ejb3.container.ContainerInterfaceImpl.prepareStart(ContainerInterfaceImpl.java:438)

at com.sap.engine.services.deploy.server.utils.container.ContainerWrapper.prepareStart(ContainerWrapper.java:508)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:279)

at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:242)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:435)

at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhases(ApplicationTransaction.java:478)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesSequentially(ParallelAdapter.java:315)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhases(StartTransaction.java:669)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2814)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceWait(DeployServiceImpl.java:3191)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationOnInstanceAndWaitAuth(DeployServiceImpl.java:3353)

at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:2726)

at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:109)

at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:80)

at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:48)

at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:84)

at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:108)

at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:72)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:1138)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:1027)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:815)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deployInternal(DeployerImpl.java:450)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:224)

at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:904)

at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:459)

at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:69)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:72)

at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:43)

at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:983)

at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:59)

at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:55)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122)

at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)

at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)

Caused by: javax.jms.InvalidDestinationException: queue:///CRRS.BROKER.REQ.UPD.03

at com.sap.jms.client.session.JMSSession.createConsumer(JMSSession.java:381)

at com.sap.jms.client.connection.JMSConnectionConsumer.<init>(JMSConnectionConsumer.java:37)

at com.sap.jms.client.connection.Connection.createConnectionConsumer(Connection.java:170)

at com.sap.jms.resourceadapter.RaActivation.setUpConnectionConsumer(RaActivation.java:221)

at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:162)

... 44 more

-

After I increased the log level, I noticed there was failure in jndi lookup for the queue and connection factory. I check the jndi lookup from NWA, it is available (eg. jms_vendor_queues_local/sap.com/CRRSRatingEAR/CRRS.BROKER.REQ.UPD.02)

-

#2.0 #2019 10 06 18:52:20:595#+0800#Info#com.sap.jms.resourceadapter.ResourceAdapterImpl#

#BC-JAS-JMS#jms#C0007F00000101E2000000AE0000161C#22411250000000044##com.sap.jms.resourceadapter.ResourceAdapterImpl#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Starting activation of JMS resource adapter endpoint factory. ActivationSpec is : applicationName=sap.com/CRRSRatingEAR,connectionFactoryName : QCF_1,mAcknowledgeMode : null,maxPoolSize : 50,mClientId : null,mDestinationName : CRRS.BROKER.REQ.UPD.02,mDestinationType : javax.jms.Queue,minPoolSize : 0,mMessageSelector : null,mSubscriptionDurability : null,mSubscriptionName : null,mSAPMDBFailoverActivation : FALSE,mReconnectAttempts : 30,mSleepBetweenAttempts : 5000,mParallelConsumers : 1#

#2.0 #2019 10 06 18:52:20:641#+0800#Info#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000AF0000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Attempt for lookup of destination failed. That could happen for 6.40 applications without application name.An attempt will be performed without the application name. The JNDI name is : jms_vendor_queues_local/sap.com/CRRSRatingEAR/CRRS.BROKER.REQ.UPD.02#

#2.0 #2019 10 06 18:52:20:646#+0800#Info#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B00000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Performing JNDI lookup for obtaining connectionFactory : jms_vendor_factory_local/sap.com/CRRSRatingEAR/QCF_1#

#2.0 #2019 10 06 18:52:20:652#+0800#Info#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B10000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

First attempt for lookup failed. That could happen for 6.40 application without application name. We will continue with the fallback chain. The JNDI lookup is : jms_vendor_factory_local/sap.com/CRRSRatingEAR/QCF_1#

#2.0 #2019 10 06 18:52:20:652#+0800#Info#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B20000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Performing JNDI lookup for obtaining connectionFactory : jms_vendor_factory_global/QCF_1#

#2.0 #2019 10 06 18:52:20:652#+0800#Warning#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B30000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Attempt for lookup without application name failed. An attempt will be performed to use the default connectionFactory instead of the one supplied during deployment. The JNDI name is : jms_vendor_factory_global/QCF_1#

#2.0 #2019 10 06 18:52:20:652#+0800#Debug#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B40000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Will try to lookup factory with lookupString jmsfactory/default/QueueConnectionFactory#

#2.0 #2019 10 06 18:52:20:653#+0800#Info#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B50000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Performing JNDI lookup for obtaining connectionFactory : jmsfactory/default/QueueConnectionFactory#

#2.0 #2019 10 06 18:52:20:846#+0800#Debug#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B60000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

JMS version is 1.1#

#2.0 #2019 10 06 18:52:20:846#+0800#Debug#com.sap.jms.resourceadapter.RaActivation#

#BC-JAS-JMS#jms#C0007F00000101E2000000B70000161C#22411250000000044##com.sap.jms.resourceadapter.RaActivation#Administrator#72##6B2BDCD600A31004BF1FACB5979ACAC2#6b2bdcd600a31004bf1facb5979acac2#6b2bdcd600a31004bf1facb5979acac2#0#Thread[RMI/IIOP Worker [2],5,Dedicated_Application_Thread]#Plain##

Exception listener was set#

-

I have run out of ideas on what is wrong. Please help.

Thanks.

former_member482483 · ‎12-01-2011

Hi,

I have run diagnosis tool and from the output file, I notice the following error :

-

ResolverManager was not able to return an instance of object factory with name: com.ibm.mq.jms.MQQueueConnectionFactoryFactory

Caught java.lang.ClassNotFoundException: com.ibm.mq.jms.MQQueueConnectionFactoryFactory

-

Loader Info -

ClassLoader name: [service:jms_provider]

Loader hash code: 199d4a86

Living status: alive

Direct parent loaders:

[system:Frame]

[library:tc_jemmodel~lib]

[service:naming]

[service:jmx]

[library:tc_jej2eedescriptors~lib]

[library:jms]

[library:antlr]

[service:security]

[service:cross]

Resources:

D:\usr\sap\C12\J02\j2ee\cluster\bin\services\jms_provider\lib\private\sap.com_tcje_{jms_provider}impl.jar

-

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:278)

at com.sap.engine.boot.loader.MultiParentClassLoader.loadClass(MultiParentClassLoader.java:247)

at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:367)

at java.lang.Class.forName0(Native Method)

at java.lang.Class.forName(Class.java:247)

at com.sap.engine.system.naming.provider.ResolverManager.findObjectFactory(ResolverManager.java:376)

at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl._getObjectInstance(ObjectFactoryBuilderImpl.java:66)

at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl.access$100(ObjectFactoryBuilderImpl.java:33)

at com.sap.engine.system.naming.provider.ObjectFactoryBuilderImpl$DispatchObjectFactory.getObjectInstance(ObjectFactoryBuilderImpl.java:228)

at javax.naming.spi.NamingManager.getObjectInstance(NamingManager.java:283)

at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:559)

at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:619)

at javax.naming.InitialContext.lookup(InitialContext.java:392)

at com.sap.jms.resourceadapter.RaInitialContextDecorator.lookup(RaInitialContextDecorator.java:61)

at com.sap.jms.resourceadapter.RaActivation.lookupConnectionFactory(RaActivation.java:638)

at com.sap.jms.resourceadapter.RaActivation.setupConnectionFactory(RaActivation.java:569)

at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:152)