Deployment of Message Driven Bean fails

[Former Member]

Hi guys,

i use MQSeries as JMS Provider.

The Application (ear) has the following structure :

MDBApp.ear

contains

mqseries1.jar ,mqseries2.jar, mqseries3.jar , .. ( In the previous Version of NetWeaver is used a deployable Server library and referenced it from the jms-factories.xml )

mdb.jar (contains the Message Driven Bean)

Note :

the jms-resources.xml has the following content :

<?xml version="1.0" encoding="UTF-8"?>

<jms-resources xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="jms-resources.xsd">

<connection-factory>

<name>TestFactory</name>

<object-factory-type>

<object-factory-name>com.ibm.mq.jms.MQXAQueueConnectionFactoryFactory</object-factory-name>

<class-name>com.ibm.mq.jms.MQXAQueueConnectionFactory</class-name>

<property>

<config-property-name>HOST</config-property-name>

<config-property-value>anIPAdress</config-property-value>

</property>

<property>

<config-property-name>QMGR</config-property-name>

<config-property-value>aQueueManagerID</config-property-value>

</property>

<property>

<config-property-name>PORT</config-property-name>

<config-property-value>aPort</config-property-value>

</property>

<property>

<config-property-name>TRAN</config-property-name>

<config-property-value>1</config-property-value>

</property>

</object-factory-type>

</connection-factory>

<destination>

<name>RA.IBMSOLLIST.ASSOLLIST.001</name>

<type>javax.jms.Queue</type>

<external-destination-type>

<link-connection-factory>TestFactory</link-connection-factory>

</external-destination-type>

</destination>

</jms-resources>

The Message Driven Bean code :

@MessageDriven(activationConfig = {

@ActivationConfigProperty(propertyName = "destinationType",

propertyValue = "javax.jms.Queue"),

@ActivationConfigProperty(propertyName = "destination",

propertyValue = "RA.IBMSOLLIST.ASSOLLIST.001"),

@ActivationConfigProperty(propertyName =

"connectionFactoryName", propertyValue = "TestFactory")

})

public class VMRaTestMessageDBean implements MessageListener {

/* (non-Javadoc)

• @see javax.jms.MessageListener#onMessage(javax.jms.Message)

*/

public void onMessage(Message arg0) {

// TODO Auto-generated method stub

}

}

The SDM gets following warning/error :

Description:

1. Exception has been returned while the 'vmtubes.de/ra_testmdb~ear' was starting. Warning/Exception :

[ERROR CODE DPL.DS.6193] Error while ; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 2198950:com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean vmtubes.de/ra_testmdb_{ear*annotation|vmtubes.de}ra_testmdb~ejb.jar*annotation|VMRaTestMessageDBean

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

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

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

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

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

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

at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Caused by: com.sap.engine.services.ejb3.container.ActionException: Cannot activate endpoint for message-driven bean vmtubes.de/ra_testmdb_{ear*annotation|vmtubes.de}ra_testmdb~ejb.jar*annotation|VMRaTestMessageDBean

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

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

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

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

... 34 more

Caused by: javax.resource.NotSupportedException: javax.resource.spi.UnavailableException: The destination RA.IBMSOLLIST.ASSOLLIST.001 cannot be looked up. Last attempt performed : jms_vendor_queues_global/RA.IBMSOLLIST.ASSOLLIST.001

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

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

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

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

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

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

... 37 more

Caused by: javax.resource.spi.UnavailableException: The destination RA.IBMSOLLIST.ASSOLLIST.001 cannot be looked up. Last attempt performed : jms_vendor_queues_global/RA.IBMSOLLIST.ASSOLLIST.001

at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:345)

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

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

... 42 more

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of RA.IBMSOLLIST.ASSOLLIST.001.

at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)

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

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

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

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

at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:343)

... 44 more

I use NetWeaver CE 7.1 SP05 .

Locke

[Vlado · Accepted solution]

Hi Locke,

How do you deploy the jms-resources.xml - as part of the MDBApp.ear, as part of another EAR, or standalone (i.e. via Telnet)?

Another thing is, you're missing the <library-name> tag. This should contain the name of the JMS Library which you should have created in advance using the DEPLOY_JMS_LIBRARY telnet command. This library should contain all MQSeries jars (not the MDBApp.ear).

More info: [Using a Third-Party JMS Provider|http://help.sap.com/saphelp_nwce10/helpdata/en/46/6e52823abf7185e10000000a114a6b/frameset.htm].

HTH!

\-- Vladimir

[Former Member · Accepted solution]

Hi Vladimir,

I deploy the jms-resources.xml as part of the MDBApp.ear .

I was not shure how to deploy a Java EE library.

That was the reason for my Post "J2EE Server Component Libary also available in CE 7.1 ?".

Maybe there is another problem ,too.

Interesting is this part of the Stacktrace :

Caused by: javax.resource.spi.UnavailableException: The destination RA.IBMSOLLIST.ASSOLLIST.001 cannot be looked up. Last attempt performed : jms_vendor_queues_global/RA.IBMSOLLIST.ASSOLLIST.001

at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:345)

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

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

... 42 more

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of RA.IBMSOLLIST.ASSOLLIST.001.

at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)

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

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

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

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

at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:343)

... 44 more

I think , that the jndiname of the destination is wrong.I declare it via the Annotation '@ActivationConfigProperty(propertyName = "destination",

propertyValue = "RA.IBMSOLLIST.ASSOLLIST.001"' in the MDB!

On monday i will test all these things and give you a feedback.

Thank you Vladimir

[Vlado · Accepted solution]

>

> Interesting is this part of the Stacktrace :
> 
> Caused by: javax.resource.spi.UnavailableException: The destination RA.IBMSOLLIST.ASSOLLIST.001 cannot be looked up. Last attempt performed : jms_vendor_queues_global/RA.IBMSOLLIST.ASSOLLIST.001
> at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:345)
> at com.sap.jms.resourceadapter.RaActivation.activate(RaActivation.java:121)
> at com.sap.jms.resourceadapter.ResourceAdapterImpl.endpointActivation(ResourceAdapterImpl.java:101)
> ... 42 more
> Caused by: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of RA.IBMSOLLIST.ASSOLLIST.001.
> at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:584)
> at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:343)
> at com.sap.engine.services.jndi.implclient.ClientContext.lookup(ClientContext.java:637)
> at javax.naming.InitialContext.lookup(InitialContext.java:351)
> at javax.naming.InitialContext.lookup(InitialContext.java:351)
> at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:343)
> ... 44 more
> 
> I think , that the jndiname of the destination is wrong.I declare it via the Annotation '@ActivationConfigProperty(propertyName = "destination",
> propertyValue = "RA.IBMSOLLIST.ASSOLLIST.001"' in the MDB!
> 

I suppose the reason for this is that the JMS resources are not created successfully, because of the missing JMS Library.

Let's see how it works after you apply the steps on the help page.

Cheers,

\-- Vladimir

[Former Member · Accepted solution]

Hi Vladimir,

the library is deployed and the <library-name> is set in the jms-resources.xml but the deployment ends still with a warning.

But the warning differs.

I have used the deploy_jms_library telnet command to deploy the MQSerieslibrary.

It is deployt definitely , because I see it in the 'Java Class Loader Viewer'(NetWeaver Administrator).

Illegal destination! What does that mean ?

The destination is the corresponding Queue, but why illegal???

For the Info :

The jms-spec version 1.0.2b will be used.

Is this a problem?

The Stacktrace :

Description:

1. Exception has been returned while the 'vmtubes.de/ra_testmdb~ear' was starting. Warning/Exception :

[ERROR CODE DPL.DS.6193] Error while ; nested exception is:

com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 2198950:com.sap.engine.services.deploy.container.DeploymentException: Cannot activate endpoint for message-driven bean vmtubes.de/ra_testmdb_{ear*annotation|vmtubes.de}ra_testmdb~ejb.jar*annotation|VMRaTestMessageDBean

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

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

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

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

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

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

at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

at com.sap.engine.interfaces.cross.AbstractCrossMessage.run(AbstractCrossMessage.java:25)

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

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

Caused by: com.sap.engine.services.ejb3.container.ActionException: Cannot activate endpoint for message-driven bean vmtubes.de/ra_testmdb_{ear*annotation|vmtubes.de}ra_testmdb~ejb.jar*annotation|VMRaTestMessageDBean

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

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

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

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

... 32 more

Caused by: javax.resource.NotSupportedException: javax.resource.spi.UnavailableException: javax.jms.InvalidDestinationException: Illegal destination!

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

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

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

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

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

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

... 35 more

Caused by: javax.resource.spi.UnavailableException: javax.jms.InvalidDestinationException: Illegal destination!

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

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

... 40 more

Caused by: javax.jms.InvalidDestinationException: Illegal destination!

at com.sap.jms.client.session.Session.createConsumer(Session.java:1807)

at com.sap.jms.client.session.Session.createConsumer(Session.java:1795)

at com.sap.jms.client.connection.ConnectionConsumer.<init>(ConnectionConsumer.java:124)

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

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

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

... 41 more

-- Locke

[Vlado · Accepted solution]

Hi Locke,

Looks like we are now one step forward; at least the JMS resources seem to have been created.

Please increase the severity for com.sap.jms.* to INFO and look for a trace like this:

"Connection, destination and serverSession pool have been initialized correctly. Delivery of JMS messages will be started."

It should be followed by the values of the connection, destination, etc. You could post the whole output here.

\-- Vladimir

P.S. What do you mean by "The jms-spec version 1.0.2b will be used."? CE 7.1 is Java EE 5 compatible and hence supports the JMS 1.1 standard.

[Former Member · Accepted solution]

Hi Vladimir,

here the output

Connection, destination and serverSession pool have been initialized correctly. Delivery of JMS messages will be started.Connection = ================================== Connection ==================================

ID 9444418335539227

Type (Generic)Connection

Mode STOPPED

isClosed NO

ExceptionListener com.sap.jms.resourceadapter.RaActivation12fa82b

client = com.sap.jms.server.remote.JMSRemoteClientImpl12e0345

server = RMI_P4: Local Dynamic Stub for impl -> com.sap.jms.server.remote.JMSRemoteServerImpl18bdfc4

-

---

P4 Remote Object Info : com.sap.engine.services.rmi_p4.server.P4ServerObjectInfo11c

|- broker id : -752547698

|- server id : 2198950

|- client Id : -1

|- local Id : 2198950

|- is redirectable : false

|- redir Ident :

|- factory Name : null

|- objId : null

|- server loader name : null

|- connected : false

|- supportOptimization : true

|- protocol : 76 31 v1

Remote Interfaces :

Interface : [0] = com.sap.jms.server.remote.JMSRemoteServer

Interface : [1] = com.sap.engine.services.rmi_p4.interfaces.P4Notification

=========================================

Connection profiles :

connection profile : [0] = None:195.233.66.25:50004

=========================================

packetFactory = com.sap.jms.protocol.PacketFactoryImpl1c9b533

thread pool = com.sap.engine.core.service630.context.core.thread.ThreadSystemImpl1974b10

isClosed = false

runFlag = true

isRunning = true

-

---

ConnectionMetaData -

---

JMSVersion 1.1

PorviderVersion Version 1.0

SupportedJMSXProperties JMSXGroupID, JMSXGroupSeq

================================================================================

com.sap.jms.client.connection.RemoteQueueConnection1c12707 isUsed = true, destination = queue:///RA.IBMSOLLIST.ASSOLLIST.001, pool = com.sap.jms.resourceadapter.RaServerSessionPool1e948c0, activation spec = applicationName=vmtubes.de/ra_testmdb~ear,connectionFactoryName : Testfactory,mAcknowledgeMode : null,maxPoolSize : 50,mClientId : null,mDestinationName : RA.IBMSOLLIST.ASSOLLIST.001,mDestinationType : javax.jms.Queue,minPoolSize : 0,mMessageSelector : null,mSubscriptionDurability : null,mSubscriptionName : null,mReconnectAttempts : 10,mSleepBetweenAttempts : 1000,mParallelConsumers : 1

Also interesting these Logentries :

1.

java.lang.ClassCastException: class javax.naming.Reference:null incompatible with interface javax.jms.Destination:library:jmscom.sap.engine.boot.loader.ResourceMultiParentClassLoader1a5d6d6alive-

at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:320)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

at com.sap.engine.interfaces.cross.AbstractCrossMessage.run(AbstractCrossMessage.java:25)

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

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

2.

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/vmtubes.de/ra_testmdb~ear/RA.IBMSOLLIST.ASSOLLIST.001

-- Locke

[Former Member · Accepted solution]

Hi Vladimir,

do you have some Infos according to that behaviour?

Everything I try ends with the same exception.

Locke

[Vlado · Accepted solution]

Hi Locke,

Please try these two things:

1. Search for this string in the traces:

"JMS Connector Container Application: vmtubes.de/ra~test~mdb~ear destination name: RA.IBMSOLLIST.ASSOLLIST.001"

and post here all its occurrences.

2. Go to Telnet console and execute the following commands:

add naming
lookup jms_vendor_queues_local/vmtubes.de/ra~test~mdb~ear/RA.IBMSOLLIST.ASSOLLIST.001

This should give you the class name of the destination bound at that location - say a.b.c.QueueImpl.

You can then look for this class in the registered classloaders using the command:

llr -all -f a/b/c/QueueImpl.class

Note the replacement of '.' with '/' and the extension .class.

Please provide the output of these commands too.

Cheers,

\-- Vladimir

[Former Member · Accepted solution]

Hi Vladimir,

i can't find the string "JMS Connector Container Application: vmtubes.de/ra_testmdb~ear destination name: RA.IBMSOLLIST.ASSOLLIST.001" in the traces.

These are all the logentries while the deployment (read the entries from top to buttom):

Starting activation of JMS resource adapter endpoint factory. ActivationSpec is : applicationName=vmtubes.de/ra_testmdb~ear,connectionFactoryName : Testfactory,mAcknowledgeMode : null,maxPoolSize : 50,mClientId : null,mDestinationName : RA.IBMSOLLIST.ASSOLLIST.001,mDestinationType : javax.jms.Queue,minPoolSize : 0,mMessageSelector : null,mSubscriptionDurability : null,mSubscriptionName : null,mReconnectAttempts : 10,mSleepBetweenAttempts : 1000,mParallelConsumers : 1

Performing JNDI lookup for obtaining connectionFactory : jms_vendor_factory_local/vmtubes.de/ra_testmdb~ear/Testfactory

First attempt for lookup failed. That could happen for 6.40 applpication without application name. We will continute with the fallback chain. The JNDI lookup is : jms_vendor_factory_local/vmtubes.de/ra_testmdb~ear/Testfactory

Performing JNDI lookup for obtaining connectionFactory : jms_vendor_factory_global/Testfactory

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/Testfactory

Performing JNDI lookup for obtaining connectionFactory : jmsfactory/default/XAQueueConnectionFactory

JMS connection created:

================================== Connection ==================================

ID 9444418335539219

Type (Generic)Connection

Mode STOPPED

isClosed NO

client = null

server = com.sap.jms.server.remote.JMSRemoteServerImpl5ec877

packetFactory = com.sap.jms.protocol.PacketFactoryImpl12e8d47

thread pool = null

isClosed = false

runFlag = true

isRunning = true

-

---

ConnectionMetaData -

---

JMSVersion 1.1

PorviderVersion Version 1.0

SupportedJMSXProperties JMSXGroupID, JMSXGroupSeq

================================================================================

com.sap.jms.client.connection.RemoteQueueConnection13d601c isUsed = false

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/Testfactory

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/vmtubes.de/ra_testmdb~ear/RA.IBMSOLLIST.ASSOLLIST.001

java.lang.ClassCastException: class javax.naming.Reference:null incompatible with interface javax.jms.Destination:library:jmscom.sap.engine.boot.loader.ResourceMultiParentClassLoader389922alive

at com.sap.jms.resourceadapter.RaActivation.setupDestination(RaActivation.java:320)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Connection, destination and serverSession pool have been initialized correctly. Delivery of JMS messages will be started.Connection = ================================== Connection ==================================

ID 9444418335539219

Type (Generic)Connection

Mode STOPPED

isClosed NO

ExceptionListener com.sap.jms.resourceadapter.RaActivation1fe79

client = com.sap.jms.server.remote.JMSRemoteClientImpl857822

server = RMI_P4: Local Dynamic Stub for impl -> com.sap.jms.server.remote.JMSRemoteServerImpl18f254f

-

---

P4 Remote Object Info : com.sap.engine.services.rmi_p4.server.P4ServerObjectInfo100

|- broker id : -752547698

|- server id : 2198950

|- client Id : -1

|- local Id : 2198950

|- is redirectable : false

|- redir Ident :

|- factory Name : null

|- objId : null

|- server loader name : null

|- connected : false

|- supportOptimization : true

|- protocol : 76 31 v1

Remote Interfaces :

Interface : [0] = com.sap.jms.server.remote.JMSRemoteServer

Interface : [1] = com.sap.engine.services.rmi_p4.interfaces.P4Notification

=========================================

Connection profiles :

connection profile : [0] = None:195.233.66.25:50004

=========================================

packetFactory = com.sap.jms.protocol.PacketFactoryImple9cc66

thread pool = com.sap.engine.core.service630.context.core.thread.ThreadSystemImpl1b57cfa

isClosed = false

runFlag = true

isRunning = true

-

---

ConnectionMetaData -

---

JMSVersion 1.1

PorviderVersion Version 1.0

SupportedJMSXProperties JMSXGroupID, JMSXGroupSeq

================================================================================

com.sap.jms.client.connection.RemoteQueueConnection16a7da2 isUsed = true, destination = queue:///RA.IBMSOLLIST.ASSOLLIST.001, pool = com.sap.jms.resourceadapter.RaServerSessionPool5e2ae5, activation spec = applicationName=vmtubes.de/ra_testmdb~ear,connectionFactoryName : Testfactory,mAcknowledgeMode : null,maxPoolSize : 50,mClientId : null,mDestinationName : RA.IBMSOLLIST.ASSOLLIST.001,mDestinationType : javax.jms.Queue,minPoolSize : 0,mMessageSelector : null,mSubscriptionDurability : null,mSubscriptionName : null,mReconnectAttempts : 10,mSleepBetweenAttempts : 1000,mParallelConsumers : 1

JMS session created:

=================================== Session ====================================

ID: 17

Type: (Generic)Session

ConnectionID: 9444418335539219

AcknowledgeMode: Transacted session!

================================================================================

ActivationSpec could not be deployed/started due to internal problem, clean up will be performed, the activation spec was applicationName=vmtubes.de/ra_testmdb~ear,connectionFactoryName : Testfactory,mAcknowledgeMode : null,maxPoolSize : 50,mClientId : null,mDestinationName : RA.IBMSOLLIST.ASSOLLIST.001,mDestinationType : javax.jms.Queue,minPoolSize : 0,mMessageSelector : null,mSubscriptionDurability : null,mSubscriptionName : null,mReconnectAttempts : 10,mSleepBetweenAttempts : 1000,mParallelConsumers : 1

javax.resource.spi.UnavailableException: javax.jms.InvalidDestinationException: Illegal destination!

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

at com.sap.engine.services.deploy.server.application.ParallelAdapter.super_MakeAllPhases(ParallelAdapter.java:337)

at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:550)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:251)

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:392)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Caused by: javax.jms.InvalidDestinationException: Illegal destination!

at com.sap.jms.client.session.Session.createConsumer(Session.java:1807)

at com.sap.jms.client.session.Session.createConsumer(Session.java:1795)

at com.sap.jms.client.connection.ConnectionConsumer.<init>(ConnectionConsumer.java:124)

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

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

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

... 43 more

An attempt to stop message delivery will be performed. Activation request was applicationName=vmtubes.de/ra_testmdb~ear,connectionFactoryName : Testfactory,mAcknowledgeMode : null,maxPoolSize : 50,mClientId : null,mDestinationName : RA.IBMSOLLIST.ASSOLLIST.001,mDestinationType : javax.jms.Queue,minPoolSize : 0,mMessageSelector : null,mSubscriptionDurability : null,mSubscriptionName : null,mReconnectAttempts : 10,mSleepBetweenAttempts : 1000,mParallelConsumers : 1

JMS session closed:

=================================== Session ====================================

ID: 17

Type: (Generic)Session

ConnectionID: 9444418335539219

AcknowledgeMode: Transacted session!

================================================================================

Connection context doesn't exists ! id =

Removing unreferenced connection ID =

Connection context doesn't exists ! id =

Connection closed:

================================== Connection ==================================

ID 9444418335539219

Type (Generic)Connection

Mode STOPPED

isClosed YES

client = com.sap.jms.server.remote.JMSRemoteClientImpl857822

server = RMI_P4: Local Dynamic Stub for impl -> com.sap.jms.server.remote.JMSRemoteServerImpl18f254f

-

---

P4 Remote Object Info : com.sap.engine.services.rmi_p4.server.P4ServerObjectInfo100

|- broker id : -752547698

|- server id : 2198950

|- client Id : -1

|- local Id : 2198950

|- is redirectable : false

|- redir Ident :

|- factory Name : null

|- objId : null

|- server loader name : null

|- connected : false

|- supportOptimization : true

|- protocol : 76 31 v1

Remote Interfaces :

Interface : [0] = com.sap.jms.server.remote.JMSRemoteServer

Interface : [1] = com.sap.engine.services.rmi_p4.interfaces.P4Notification

=========================================

Connection profiles :

connection profile : [0] = None:195.233.66.25:50004

=========================================

packetFactory = com.sap.jms.protocol.PacketFactoryImple9cc66

thread pool = com.sap.engine.core.service630.context.core.thread.ThreadSystemImpl1b57cfa

isClosed = true

runFlag = false

isRunning = true

-

---

ConnectionMetaData -

---

JMSVersion 1.1

PorviderVersion Version 1.0

SupportedJMSXProperties JMSXGroupID, JMSXGroupSeq

================================================================================

com.sap.jms.client.connection.RemoteQueueConnection16a7da2 isUsed = true

Here the Telnet output :

>lookup jms_vendor_queues_local/vmtubes.de/ra_testmdb~ear/RA.IBMSOLLIST.ASSOLLIST.001

Trying to connect...

Connected.

[Shell -> LOOKUP] Location : /jms_vendor_queues_local/vmtubes.de/ra_testmdb~ear

/RA.IBMSOLLIST.ASSOLLIST.001

[Shell -> LOOKUP] Contains : Reference Class Name: com.ibm.mq.jms.MQQueue

Type: VER

Content: 1

Type: EXP

Content: -2

Type: PRI

Content: -2

Type: PER

Content: -2

Type: CCS

Content: 1208

Type: TC

Content: 0

Type: ENC

Content: 273

Type: FIQ

Content: 1

Type: QU

Content: RA.IBMSOLLIST.ASSOLLIST.001

Type: QMGR

Content:

[Shell -> LOOKUP] Class name : javax.naming.Reference

>llr -all -f com/ibm/mq/jms/MQQueue.class

jar:file:/C:/usr/sap/J2E/J00/j2ee/cluster/bin/ext/MQSLibrary/com.ibm.mq.jms.jar!

/com/ibm/mq/jms/MQQueue.class

jar:file:/C:/usr/sap/J2E/J00/j2ee/cluster/apps/vmtubes.de/mq%7Ebase%7Eserver%7El

ib/app_libraries_container/com.ibm.mq.jms.jar!/com/ibm/mq/jms/MQQueue.class

Locke

[Former Member · Accepted solution]

Hi Vladimir,

when you look to that part of the deployment stacktrace, there is something suspicious :

Performing JNDI lookup for obtaining connectionFactory : jms_vendor_factory_local/vmtubes.de/ratestmdb~ear/Testfactory
First attempt for lookup failed. That could happen for 6.40 applpication without application name. We will continute with the fallback chain. The JNDI lookup is : jms_vendor_factory_local/vmtubes.de/ratestmdb~ear/Testfactory

I see in the jndi browser, that the QueueConnectionFactory of MQSeries is on that path jms_vendor_factory_local/vmtubes.de/ra_testmdb~ear/Testfactory in the JNDI Registry.

The Application is a CE 7.1 Application, therefore this part That could happen for 6.40 applpication without application name is irrelavant

Nevertheless it could't be found! Why that ??

This part of the stacktrace is also suspicious :

Performing JNDI lookup for obtaining connectionFactory : jms_vendor_factory_global/Testfactory
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/Testfactory

When I read that part i decided to deploy the jms-resources.xml via Telnet, to get a global/shared jms resource.

I deployed the jms-resources.xml with the Telnet command 'deploy_jms_resource path/to/jms-resources.xml' .

After that I can see the QueueConnectionFacory on the Path 'jms_vendor_factory_global/Testfactory' in the JNDI Registry.

While deployment the same problem !!!!!

I don't understand the clause 'Attempt for lookup without application name failed. .....'

What must i do for avoiding this problem???

Locke

Edited by: Locke Cihan on Sep 27, 2008 12:36 PM

Edited by: Locke Cihan on Sep 27, 2008 12:39 PM

[Vlado · Accepted solution]

Hi Locke,

Sorry for the delay.

This is really strange now. The root cause of the problem seems to lie in the inability to look up the MQSeries Testfactory although, as you say, it's bound at the appropriate location in the JNDI tree. I'd suggest that you open a support ticket with SAP as this will most certainly require a connection to your system to investigate this issue.

To speed up processing, please:

- delete all log and trace files under /usr/sap/<SID>/<instance>/j2ee/cluster/server<N>/log (back them up for your reference) and deploy the application on clean

- zip the log directory and attach it to the ticket

- also attach the output of the following telnet command (from the naming group): lsn -c

- indicate whether you use a clustered or a single-node server

- refer to this thread in the ticket.

\-- Vladimir

[Former Member · Accepted solution]

Hi Vladimir,

thanks a lot for your help.

Locke

[Vlado · Accepted solution]

Hi Locke,

Can you also provide the ticket number when you create it, so that we can keep track of it and eventually update this thread with the outcome of our investigations?

\-- Vladimir

[Former Member · Accepted solution]

Hi Vladimir,

i'm waiting for a new major release of CE 7.1 EHP1.Do you have some information when it will be offered?

I need the Business Rules Management and the ability to use JPA in WebDynpro without using EJB's.

As far as I know a beta version of EHP1 will be offered at the moment.

Therefore I must wait with the ticket.

As soon as i get the proper CE 7.1 EHP1 release, i will open a new ticket and post you the number.

Another problem at the moment is, that i just have a local installation of CE 7.1 .

Our NetWeaver environment will be provided in winter.

Locke

[Vlado · Accepted solution]

Hi Locke,

Current plans are to release CE 7.1 EHP1 in the end of this year. A beta version is already available for trial [here|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00846edd-355b-2b10-f38c-df94ec96eb74], and I believe it's also available for download on the [SAP Service Marketplace|http://service.sap.com] (maybe for select customers/partners only).

HTH!

-- Vladimir

[Former Member · Accepted solution]

Hi Vladimir,

thanks for the information.

I will post you the ticket number as soon as the new EHP1 release is available.

You're very helpful, thanks.

Cheers

Locke

[Former Member]

Just wanted to add my $.02 on the "com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of ..." error. This happened to me when the J2EE license was still good, but the Netweaver license had expired. Fixing the license problem fixed the error.