Skip to Content
avatar image
Former Member

Error while deploying a message driven bean

I am getting the following errors while deploying message driven bean example(WAS). I have alreday configured connection factories/topics/ queues.

=> deployed with warning : file:/C:/DOCUME1/SHILPA1/LOCALS~1/Temp/temp25375MessageEAR.ear

Finished with warnings: development component 'MessageEAR'/'sap.com'/'localhost'/'2007.01.17.09.43.36':

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

java.rmi.RemoteException: Error occurred while starting application sap.com/MessageEAR and wait. Reason: Clusterwide exception: server ID 4380950:com.sap.engine.services.jmsconnector.exceptions.BaseDeploymentException: Naming error.

at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.loadFactory(ContainerImpl.java:1902)

at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.prepareStart(ContainerImpl.java:715)

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

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:301)

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

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

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

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

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

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

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:304)

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

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

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

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

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:100)

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

Caused by: javax.naming.NoInitialContextException: Cannot instantiate class: [Root exception is java.lang.ClassNotFoundException: ]

at com.sap.engine.system.naming.provider.ResolverManager.findInitialContextFactory(ResolverManager.java:489)

at com.sap.engine.system.naming.provider.DefaultInitialContext._getDefaultInitCtxt(DefaultInitialContext.java:60)

at com.sap.engine.system.naming.provider.DefaultInitialContext.<init>(DefaultInitialContext.java:46)

at com.sap.engine.system.naming.provider.DefaultInitialContextFactory.getInitialContext(DefaultInitialContextFactory.java:41)

at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662)

at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:243)

at javax.naming.InitialContext.init(InitialContext.java:219)

at javax.naming.InitialContext.<init>(InitialContext.java:195)

at com.sap.engine.services.jmsconnector.deploy.ContainerImpl.loadFactory(ContainerImpl.java:1899)

... 20 more

Caused by: java.lang.ClassNotFoundException:

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

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

at com.sap.engine.system.naming.provider.ResolverManager.findInitialContextFactory(ResolverManager.java:472)

... 28 more

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

Please provide some help.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Jan 17, 2007 at 03:43 PM

    Hi,

    seems you enterprise bean is not correct. It looks like that it can't create the InitialContext.

    Maybe the JNDI name is not correct.

    regards

    daniel

    Add comment
    10|10000 characters needed characters exceeded

    • No apologies necessary, I guess 😊

      The important thing is that the problem is solved and also it is hopefully clear now when to lookup with java:comp/env/ and when - from the naming root.

      -Vladimir

  • Jan 17, 2007 at 04:03 PM

    Hi Shilpa,

    You have to specify the initial context factory in the jms-factories.xml. It should be:

    <initial-context-factory>com.sap.engine.services.jndi.InitialContextFactoryImpl</initial-context-factory>

    Please check these links:

    http://help.sap.com/saphelp_nw04/helpdata/en/d1/259a53c73ab043a413e096e0523d54/frameset.htm

    http://help.sap.com/saphelp_nw04/helpdata/en/e8/48ef3d5e10af5ee10000000a114084/frameset.htm

    HTH!

    -Vladimir

    Add comment
    10|10000 characters needed characters exceeded