Skip to Content
0
Dec 06, 2011 at 09:18 AM

Deployment of EAR file fails due to "living child loaders" ?

66 Views

Hi,

During deployment of an EAR file on our NetWeaver CE 7.1 environment, we sometimes get the following exception and deployment fails:

[ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [company.com/project~ear]. 
[EXCEPTION]
 com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5029] Exception in operation [startApp] with application [company.com/project~ear].
at com.sap.engine.services.deploy.server.application.ApplicationTransaction.rollbackPart(ApplicationTransaction.java:619)
at [...snip...]

Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5066] Cannot remove ApplicationLoader for application [company.com/project~ear].
at com.sap.engine.services.deploy.server.DeployServiceImpl.removeLoader(DeployServiceImpl.java:1966)
at [...snip...]

Caused by: java.lang.IllegalStateException: Trial to unregister the class loader [company.com/project~ear], which has living child loaders with names:
   [company.com/anotherproject~ear]
A certain loader should NOT be unregistered if it has living child loaders. First, these child loaders should be unregistered.
at com.sap.engine.core.classload.impl0.LoadContextImpl.unregisterLoaderInternal(LoadContextImpl.java:1343)
at [...snip...]

Anyone seen this exception before? I only found one thread on SDN but that didn´t help me much

Oh, and the funny thing is: projectear and anotherprojectear have no relationship/dependency whatsoever...

I am curious to know the rootcause

Best regards,

Robin van het Hof