cancel
Showing results for 
Search instead for 
Did you mean: 

EJBDeploymentException

Former Member
0 Kudos

Hi,

I tried porting my J2EE application from websphere to SAP WAS. During deployment, got the following error.

Settings

SDM host : C8084

SDM port : 50018

URL to deploy : file:/C:/DOCUME1/ROMA1.LAU/LOCALS~1/Temp/temp3627SAPSweeps.ear

Result

=> deployed with warning : file:/C:/DOCUME1/ROMA1.LAU/LOCALS~1/Temp/temp3627SAPSweeps.ear

Finished with warnings: development component 'SAPSweeps'/'sap.com'/'localhost'/'2006.06.30.17.21.18':

Caught exception during application startup from SAP J2EE Engine's deploy service:

java.rmi.RemoteException: Error occurred while starting application sap.com/SAPSweeps and wait. Reason: Clusterwide exception: server ID 2838550:com.sap.engine.services.ejb.exceptions.deployment.EJBDeploymentException: Exception during the initialization of container boot class com.polaris.cash.sweeps.execution.mdb.AccountBalanceRequestBean0ContainerFP.

at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:990)

at com.sap.engine.services.ejb.EJBAdmin.prepareStart(EJBAdmin.java:2400)

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

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

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

at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:301)

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

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

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

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

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

at com.sap.engine.services.deploy.server.DeployServiceImplp4_Skel.dispatch(DeployServiceImplp4_Skel.java:1163)

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

at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)

at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)

at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)

Caused by: com.sap.engine.services.ejb.ContainerInitializationException: Cannot initialize message system bridge com.sap.engine.services.ejb.message.JMSBridgeFP.

at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:437)

at com.sap.engine.services.ejb.message.MessageContainer.init(MessageContainer.java:132)

at com.sap.engine.services.ejb.message.MessageContainerFP.init(MessageContainerFP.java:53)

at com.sap.engine.services.ejb.EJBAdmin.prepareLoad(EJBAdmin.java:984)

... 20 more

Caused by: com.sap.engine.services.ejb.message.JMSBridgeException: Destination name ABReqQ not found in the naming.

at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:117)

at com.sap.engine.services.ejb.message.MessageContainer.load(MessageContainer.java:435)

... 23 more

Caused by: com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during lookup operation of object with name ejbContainer/mdb/sap.com/SAPSweeps/ExecutionQCF, cannot resolve object reference. [Root exception is com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "ExecutionQCF" does not exist. Possible reasons: the connector in which ConnectionFactory "ExecutionQCF" is defined is not deployed or not started.]

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

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

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

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

at com.sap.engine.services.ejb.message.JMSBridge.registerListener(JMSBridge.java:92)

... 24 more

Caused by: com.sap.engine.services.connector.exceptions.BaseResourceException: ConnectionFactory "ExecutionQCF" does not exist. Possible reasons: the connector in which ConnectionFactory "ExecutionQCF" is defined is not deployed or not started.

at com.sap.engine.services.connector.ResourceObjectFactory.getObjectInstance(ResourceObjectFactory.java:207)

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

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

... 28 more

(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineApplOnlineDeployerImpl.performAction(DeploymentActionTypes).REMEXC)

Deployment exception : Got problems during deployment

Pl reply back ASAP.

Thx

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

I hope you are not using the same EAR file which you created for WebSphere directly onto WebAS. IF that is the case, it wont work. if everything worked fine previously on WAS then it should work on WebAS also provided you are not using anything server specific , still you would need to create the EAR which would always be WebAS specific.

Former Member
0 Kudos

Hi Roma,

Pls create a Connection factory and required JMS destinations using Visual Administrator. Or you can bundle jms-factories.xml,jms-destinations.xml along with your ear so that they are deployed.

regards,

Sujesh

Former Member
0 Kudos

Sujesh,

I tried creating Conn factory and JMS using Visual Administrator. But cannot give the same name as the application ear. How is it done using jms-factories.xml,jms-destinations.xml ?

Thanks

Former Member
0 Kudos

Hi,

Is this connector "ConnectionFactory "ExecutionQCF" does not exist. Possible reasons: the connector in which ConnectionFactory "ExecutionQCF" is defined is not deployed or not started." deployed previously or it is expected that it will be deployed together with the ejbs?

If it is deployed previously you can check its availability in the Visual Administrator:

<a href="http://help.sap.com/saphelp_nw04/helpdata/en/10/33d5cf151a52439b83c0668f8a4fc5/frameset.htm">http://help.sap.com/saphelp_nw04/helpdata/en/10/33d5cf151a52439b83c0668f8a4fc5/frameset.htm</a>

Best Regards,

Violeta