Page tree
Skip to end of metadata
Go to start of metadata

(JSTTSG)(Deploy)Problems-P97

Problem

Wrong proxy settings.

Keywords

TransportBindingException

CODE DPL.DC.3312

proxy settings

Symptoms

Offline deployment restart fails due to following error: .

"TransportBindingException: Invalid Response code (503)"

Solution

1. Make sure  that proxy settings on client and server side are correct.

HINT: On server side localhost cannot be used as a proxy server

HINT: Check SOA Middleware Global settings in netweaver .
If there is a proxy set the exclude list should be configured appropriately as well.

Sample logs

[EXCEPTION]
com.sap.engine.services.dc.cm.deploy.DeploymentException: An error occurred while restarting the server.
at com.sap.engine.services.dc.cm.deploy.impl.OfflineDeployPostProcessor.postProcess(OfflineDeployPostProcessor.java:113)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:1138)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:1027)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:815)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deployInternal(DeployerImpl.java:450)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:224)
at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:910)
at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:462)
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:983)
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:122)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:328)
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:50013/?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: javax.xml.ws.WebServiceException: Invalid Response code (503). Server http://1.1.1.1 returned message [Service Unavailable]. Http proxy info: Http proxy proxy:8080 used for host http://1.1.1.1
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:174)
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 $Proxy2482.j2EEControlCluster(Unknown Source)
at com.sap.engine.services.dc.jstartup.impl.JStartupClusterManagerImpl.restartCluster(JStartupClusterManagerImpl.java:188)
... 19 more
Caused by: com.sap.engine.services.webservices.espbase.client.bindings.exceptions.TransportBindingException: Invalid Response code (503). Server http://1.1.1.1 returned message [Service Unavailable]. Http proxy info: Http proxy proxy:8080 used for host http://1.1.1.1
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.handleSOAPResponseMessage(SOAPTransportBinding.java:582)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call_SOAP(SOAPTransportBinding.java:1369)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.callWOLogging(SOAPTransportBinding.java:990)
at com.sap.engine.services.webservices.espbase.client.bindings.impl.SOAPTransportBinding.call(SOAPTransportBinding.java:944)
at com.sap.engine.services.webservices.espbase.client.jaxws.core.WSInvocationHandler.processTransportBindingCall(WSInvocationHandler.java:168)
... 24 more