"hard reference to resource" warning on deploying an ejb web service

[Former Member]

Hi

I created an EJB Project, a session bean and a webservice on it. The session bean has a method which connects to mdm 7.1 and retrieves information from it. Built an Enterprise Application project and on deploying this I am getting the below error. Any tips on how do I get over this error.

Thanks,

KN.

*********************************************************************************************************************************************************

Description:

1. Exception has been returned while the [bms.com/test~mdmejbear] was starting. Warning/Exception :[

][ASJ.dpl_ds.006153 Error occurred while starting application [bms.com/test~mdmejbear]: It is not started successfully on server nodes [51237750]. In order to bring the server in consistent state stop operation will be performed.

Error occurred on server 51237750 during startApp of bms.com/test_{mdmejbear : Application [bms.com/test}mdmejbear] cannot be started. Reason: it has hard reference to resource [test~mdmejb] with type [application], which is not active on the server.

Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?

Error occurred on server 51237750 during startApp of bms.com/test_{mdmejbear : com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Application [bms.com/test}mdmejbear] cannot be started. Reason: it has hard reference to resource [test~mdmejb] with type [application], which is not active on the server.

Hint: 1) Is referred resource deployed? 2) Is referred resource able to start?

at com.sap.engine.services.deploy.server.ReferenceResolver.processReferenceToApplication(ReferenceResolver.java:1108)

at com.sap.engine.services.deploy.server.ReferenceResolver.processReference(ReferenceResolver.java:766)

at com.sap.engine.services.deploy.server.ReferenceResolver.beforeStartingApplication(ReferenceResolver.java:657)

at com.sap.engine.services.deploy.server.application.StartTransaction.beginCommon(StartTransaction.java:207)

at com.sap.engine.services.deploy.server.application.StartTransaction.begin(StartTransaction.java:175)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

]

Result

Status:Warning

[former_member205403]

Hi,

Please let us know have you deployed Java API on the Server ?

Regards,

Shiv

[Former Member]

Hi

Yes I have deployed the Java API on the server and infact the same set of coding has successfully run using a web dynpro application deployed on the same server. Also dependency were added by using the JAVA API component depoyed in NWDI.

Thanks,

KN.

[Former Member]

Hi

The problem has been resolved. Useful blog which heped is below:

/people/andreas.seifried/blog/2007/01/18/referencing-the-mdm-java-api-during-development-and-runtime

Thanks,

KN.

[Former Member]

On checking the build log I see these warnings. For the third warning I have put selected the Run time as well, but I dont know why thats a warning. How do I resolve these "incompatible type" warnings?

*********************************************************

WARNING: Runtime dependency to "test/mdmejb" ("bms.com") will be ignored because of an incompatible type.

[cdu] WARNING: Deploy-time dependency to "test/mdmejb" ("bms.com") will be ignored because of an incompatible type.

WARNING: Missing deploy-time dependency for hard runtime reference to "test/mdmejb" (vendor "bms.com").