Skip to Content

JAVA Server connection breaks during SM Deploy

I am applying JAVA support stacks to our JAVA instances. SUM will deploy a few components and then stop. If I look in the logs I see this error out. In the MMC the server appears to be up with nothing down. My question is what would suddenly cause the P4 connection to no longer work on the java instances. This happens repeatedly the only way around it is to restart the java server manually which then case the deploy process to fail and need restarting.

Netweaver 7.4 JAVA Only

MS Windows 2008 R2

Oracle 12.1.2

error message.

#2.0#2018 02 28 08:43:57:572#0-600#Error#com.sap.engine.services.tc~bl~deploy~api# com.sap.ASJ.dpl_api.001224###C00084ACE7B0000000000D995A4F72C3###com.sap.engine.services.tc~bl~deploy~api#####4eeac4782b7f103ec40cf5aaff83a252###Thread[Thread-11,5,main]#Plain## Could not establish connection to AS Java on [S######R3:50504]. No alive connection. Check state of the server. Check if the host and port specified are correct and AS Java is up and running. [EXCEPTION] javax.naming.NamingException: Exception during getInitialContext operation. Cannot establish connection to the remote server. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.] at com.sap.engine.services.jndi.InitialContextFactoryImpl.handleConnectionPropblem(InitialContextFactoryImpl.java:416) at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:338) at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667) at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288) at javax.naming.InitialContext.init(InitialContext.java:223) at javax.naming.InitialContext.<init>(InitialContext.java:197) at com.sap.engine.services.dc.api.session.impl.SessionImpl.getContext(SessionImpl.java:215) at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.reconnectDeployer(DeployProcessorImpl.java:1954) at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.waitResultForOfflineDeploy(DeployProcessorImpl.java:1626) at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deployItems(DeployProcessorImpl.java:903) at com.sap.engine.services.dc.api.deploy.impl.DeployProcessorImpl.deploy(DeployProcessorImpl.java:259) at com.sap.sdt.j710.deploymentmgr.DeploymentManagerImpl.deployList(DeploymentManagerImpl.java:357) at com.sap.sdt.j2ee.tools.deploymentmgr.AbstractDeploymentManager.deployDeploymentUnits(AbstractDeploymentManager.java:359) at com.sap.sdt.jspm.deployment.deploy.DeploymentManager.deployDeployableUnits(DeploymentManager.java:2044) at com.sap.sdt.jspm.deployment.deploy.DeploymentManager.deployComponents(DeploymentManager.java:3893) at com.sap.sdt.jspm.service.JspmService.updateComponents(JspmService.java:1590) at com.sap.sdt.jspm.service.JspmService.updateComponents(JspmService.java:1531) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sap.sdt.executor.step.StepExecutor.executeStep(StepExecutor.java:198) at com.sap.sdt.executor.module.ModuleExecutor.executeModule(ModuleExecutor.java:104) at com.sap.sdt.executor.action.ActionExecutor.executeModule(ActionExecutor.java:346) at com.sap.sdt.executor.action.ActionExecutor.executeAction(ActionExecutor.java:82) at com.sap.sdt.executor.usecase.UseCaseExecutor.executeOrRevokeRegularAction(UseCaseExecutor.java:592) at com.sap.sdt.executor.usecase.UseCaseExecutor.executeActionInternal(UseCaseExecutor.java:473) at com.sap.sdt.executor.usecase.UseCaseExecutor.executeAction(UseCaseExecutor.java:442) at com.sap.sdt.executor.usecase.UseCaseExecutor.executeActionInRoadmapStep(UseCaseExecutor.java:298) at com.sap.sdt.executor.usecase.UseCaseExecutor.executeRoadmapStepAction(UseCaseExecutor.java:269) at com.sap.sdt.executor.usecase.UseCaseExecutor.executeRoadmapStepActions(UseCaseExecutor.java:253) at com.sap.sdt.executor.usecase.UseCaseExecutor.executeRoadmapStep(UseCaseExecutor.java:214) at com.sap.sdt.slprotocol.uce.UseCaseExecutionThread.executeCurrentRoadmapStep(UseCaseExecutionThread.java:59) at com.sap.sdt.slprotocol.uce.UseCaseExecutionThread.run(UseCaseExecutionThread.java:35) Caused by: com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance. at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:164) at com.sap.engine.services.jndi.implclient.LoginHelper.clientSideLogin(LoginHelper.java:79) at com.sap.engine.services.jndi.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:315) ... 32 more Caused by: com.sap.engine.services.rmi_p4.P4IOException: No alive connection. Check state of the server at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:828) at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:813) at com.sap.engine.services.rmi_p4.ClientConnection.sendRequest(ClientConnection.java:362) at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.resolveInitialReference(P4ObjectBrokerClientImpl.java:123) at com.sap.engine.services.rmi_p4.RemoteBroker.resolveInitialReference(RemoteBroker.java:41) at com.sap.engine.services.security.remote.login.RemoteLoginContext.<init>(RemoteLoginContext.java:153) ... 34 more

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    Apr 03 at 04:57 AM

    Hello Troy,

    If the error persists, please check the deploy controller log on Java , it will be under /usr/sap/<SID>/<instance>/work/deploy.x.trc

    Also, check the default traces to see if it offers any clue. When you see the P4 error, please check the access points in SAP MMC under SID-> instance name and check the state of P4 port at the time.


    Regards,

    Asha

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Mar 01 at 07:26 AM

    Hi,

    This is issue with P4 port during deployment with SUM is known issue. SUM restarts Java Server several times during the deployment and yes, in some cases only stopping phase happens, and no start up occurs. In this cases, just like you did, we always recommend a manual startup of the system and then continue the deployment from the process it has ended.

    As this was a working workaround for you I would exclude other cause behind this issue. You can keep doing this manual startup in this cases, but any time you have an issue check if the same P4IOException is received. If new error/exception happens, get back here with that.

    Thanks,

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 28 at 04:47 PM

    Check Note 1891477 - PI 7.1X upgrade deployment process fails due to missing ExecutionDetails class. It looks related

    Add comment
    10|10000 characters needed characters exceeded

    • I saw that one earlier. The difference here is that I can stop and start the server at will and at the time the messages are being generated the JAVA instance can be connected to. I can stop and start the JAVA server manually then repeat the step and it will deploy a few more components before hanging again. This is a netweaver 7.4 system JSPM does not function in those systems.

      Thanks for checking though

      Troy