Symptom
SUM fails to restart Java instance during an upgrade. The following message can be found in deploy.X.trc log in the Work directory of the Application Server Java:
Caused by: com.sap.engine.services.dc.cm.server.spi.RestartServerService$RestartServerServiceException: [ERROR CODE DPL.DC.3154] An error occurred while restarting the AS Java Cluster.
at com.sap.engine.services.dc.cm.server.impl.AbstractRestartServerService.restart(AbstractRestartServerService.java:214)
at com.sap.engine.services.dc.cm.server.impl.AbstractRestartServerService.restartInSafeMode(AbstractRestartServerService.java:112)
at com.sap.engine.services.dc.cm.deploy.impl.OfflineDeployPostProcessor.postProcess(OfflineDeployPostProcessor.java:105)
... 16 more
Caused by: com.sap.engine.services.dc.jstartup.JStartupException: [ERROR CODE DPL.DC.3312] An error occurred while restarting the cluster using SAP control webservice on URI [http://localhost:5XX13/?wsdl].
at com.sap.engine.services.dc.jstartup.impl.JStartupClusterManagerImpl.restartCluster(JStartupClusterManagerImpl.java:213)
at com.sap.engine.services.dc.cm.server.impl.AbstractRestartServerService.restart(AbstractRestartServerService.java:202)
... 18 more
Caused by: This exception is wrapper of javax.xml.ws.soap.SOAPFaultException. com.sap.engine.services.webservices.espbase.client.bindings.exceptions.SOAPFaultException: Invalid parameter: No matching J2EE instance found
at com.sap.engine.services.webservices.espbase.client.bindings.impl.JAXWSUtil.processFault(JAXWSUtil.java:412)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1421)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:998)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:952)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:168)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEISyncMethod(WSInvocationHandler.java:121)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invokeSEIMethod(WSInvocationHandler.java:84)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.invoke(WSInvocationHandler.java:65)
at com.sun.proxy.$Proxy65.j2EEControlCluster(Unknown Source)
at com.sap.engine.services.dc.jstartup.impl.JStartupClusterManagerImpl.restartCluster(JStartupClusterManagerImpl.java:188)
Read more...
Environment
SAP NetWeaver Application Server Java
Product
Keywords
No matching J2EE instance found, SUM fails, deployment, AS Java, javax.xml.ws.soap.SOAPFaultException, upgrade, update, restart, sapcontrol, DIR_GLOBAL , KBA , BC-JAS-SF , Startup Framework , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview