Skip to Content
avatar image
Former Member

Deployment of Message Driven Bean fails

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"?>

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/ratestmdb~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/ratestmdbear*annotation|vmtubes.deratestmdb~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/ratestmdbear*annotation|vmtubes.deratestmdb~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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    Sep 19, 2008 at 03:50 PM

    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

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Vladimir Pavlov

      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

  • avatar image
    Former Member
    Sep 26, 2008 at 06:31 PM

    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.

    Add comment
    10|10000 characters needed characters exceeded