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

Problem

AS Java Server cannot start.

Symptom

In MMC ICM is green, AS Java instance cannot start.

Keywords

  • ICM
  • P4
  • Bind socket

Description

In ICM traces, there is Error during opening ServerSocket for RMI-P4 service:

[Thr 1113651552] *** ERROR => NiIBindSocket: SiBind failed for hdl 73/sock 27 (SI_EPORT_INUSE/98; I4; ST; 0.0.0.0:52604) [nixxi.cpp 3692]
[Thr 1113651552] *** ERROR => IcmBindService: NiBuf2Listen failed for host ldcinc6.wdf.sap.corp:52604 (rc=-4): NIESERV_USED [icxxserv_mt.2163]

Note: ICM traces are allocated in:
/usr/sap/<SID>/<Instance_Name><Instance_Number>/work/dev_icm
/usr/sap/<SID>/<Instance_Name><Instance_Number>/work/dev_icm.old

Solution

If you find Error similar to following messages in dev_icm log file:

[Thr 1113651552] Started service 52600 for protocol HTTP on host "ldcinc6.wdf.sap.corp"(on all adapters) (processing timeout=600, keep_alive_timeout=60)
[Thr 1113651552] *** ERROR => NiIBindSocket: SiBind failed for hdl 73/sock 27 (SI_EPORT_INUSE/98; I4; ST; 0.0.0.0:52604) [nixxi.cpp 3692]
[Thr 1113651552] *** ERROR => IcmBindService: NiBuf2Listen failed for host ldcinc6.wdf.sap.corp:52604 (rc=-4): NIESERV_USED [icxxserv_mt.2163]
[Thr 1113651552] *** WARNING => Could not start service 52604 for protocol P4 on host "ldcinc6.wdf.sap.corp"(on all adapters) [icxxman_mt.c 4325]

Then you have problem with opening server socket to specified port. (In example 52604).

  • Most probably some process has occupied the port.
  • Find and kill this process or restart the machine to release the port.
  • Then restart the cluster and monitor ICM logs, not to occur the same issue.
  • If the problem persists report the issue to CSN component: BC-CST-IC

Note: P4 service is not working properly because the ICM has not opened port for RMI-P4 protocol.


For details check the following wiki:
http://wiki.sdn.sap.com/wiki/display/TechTSG/%28JSTTSG%29%28P4-IIOP%29P4-P003+Exit+code+-2106

  • No labels