SAP Knowledge Base Article - Preview

2328906 - Java crash in clustered environment : appadmin service fails

Symptom

  • Java unable to start in clustered environment
  • std_serverx(/usr/sap/<SID>/<instance>work) of one of the cluster element(lets call it server node x)  has the entry : CSN Component [BC-JAS-ADM-ADM], DC Name [sap.com/appadmin] com.sap.engine.frame.ServiceException: ASJ.dpl_ds.006174 P4Object broker return null while trying to access the Deploy Service on cluster id<yyyyyyy>
  • The relevent default trace of the server node x(/usr/sap/<SID>/<instance>/j2ee/cluster/serverX/log) :

    Warning#com.sap.engine.core.cluster.impl6.p2pnio.ConnectionHolder#com.sap.ASJ.krn_clu.000105#BC-JAS-COR-CLS#kernel.sda#C0000A8C039F001B00000085000029C2#5505450000001732##com.sap.engine.core.cluster.impl6.p2pnio.ConnectionHolder####5EF3C4EC296A11E6CDD6005056A048D0#5ef3c4ec296a11e6cdd6005056a048d0#5ef3c4ec296a11e6cdd6005056a048d0#0#ClusterP2P#Plain##Cannot connect to cluster node [] host [/127.0.0.1:<port>] for [<time>] millis

    [EXCEPTION]java.io.IOException: Connection refused. Remote connection state: CONNECTED        at com.sap.engine.core.cluster.impl6.p2pnio.HandShaker.connect(HandShaker.java:178)        at com.sap.engine.core.cluster.impl6.p2pnio.ConnectionHolder.connect(ConnectionHolder.java:12)        at com.sap.engine.core.cluster.impl6.p2pnio.ConnectionHolder.access$100(ConnectionHolder.java:41)        at com.sap.engine.core.cluster.impl6.p2pnio.ConnectionHolder$1.run(ConnectionHolder.java:92)        at com.sap.engine.frame.core.thread.Task.run(Task.java:73)        at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:178)        at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:316)

  • On the server node referred by the cluster id<yyyyyyy> , you might find these logs (std_serverx.out) 

    Caused by: java.rmi.ServerException: The server process [xxxxxxx], that the client was connected with, is not working. Check its traces for details. Since the remote object is not Redirectable, client-server communication will not work. Check the logs on the client side containing this exception in order to identify the responsible application/component, which shall lookup the remote object again in order to make it operational.

            at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:406)

            at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:81)


Read more...

Environment

  SAP Netweaver Java.

Product

SAP NetWeaver Application Server for Java all versions

Keywords

appadmin,loopback,java.io.IOException, client-server,deploy service, netweaver java,cluster id, localhost, etc/host,p2pnio,ConnectionHolder,127.0.0.1,cluster node , KBA , BC-JAS-COR , Enterprise Runtime, Core J2EE 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.