Hello,
I developed an application with a BPM-, lib-, dict-, bpm-wdp (bpm-tasks with WebDynpro), another WebDynpro and two ear-DCs. The WebDynpro- and one of the ear-CDs have a dependency to the lib-DC which contains a couple of libraries such as xalan-2.7.0. When deploying the ear with the lib-dependency the deployment is successful but starting of the component fails. After a couple of hours it is suddenly running fine.
When deploying (which does an application-startup) I get the following exception:
Could not start managed object for application xxxx/yyyyyy~ear: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: [server ID 333330755:com.sap.engine.services.appclient.exceptions.BaseDeploymentException: Problem in appclient deployment. Cannot create application client environment into naming. Application "xxxx/yyyyyy~ear" will not be deployed because of NamingException.
at com.sap.engine.services.appclient.server.ApplicationClientContainer.prepareStart(ApplicationClientContainer.java:433)
....
Caused by: com.sap.engine.services.jndi.persistent.exceptions720.NameNotFoundException: Path to object does not exist at appclient-environment, the whole lookup name is appclient-environment/xxxx/yyyyyy~ear/xalan-2.7.0.
at com.sap.engine.services.jndi.implserver.ServerContextImpl.getLastContainer(ServerContextImpl.java:236)
at com.sap.engine.services.jndi.implserver.ServerContextImpl.lookup(ServerContextImpl.java:599)
On another host with same NetWeaver-version I can deploy this component and it starts up fine. Only restarting the app causes this exception and redeploying works fine again.
If I remove the lib xalan from the lib-DC the same exception shows up with some other library from the lib-DC.
We're using NetWeaver 7.2 SP9.
Any ideas are appreciated how to fix this behaviour.
Thanks