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

Problem

System with Debug Proxy installed has hanged calls via connections from current cluster ID to cluster ID 0.

Symptom

P4 connection leaks in cluster-cluster communication inside the SAP System, after Debug Proxy is enabled. Call to restarted server process in cluster-cluster communication via connection via Debug Proxy hang.

Description

Cluster connections via DEBUG proxy are not closed even if the remote side behind the proxy is restarted.

Solution

Disable DEBUG proxy and restart cluster with hanged connections to cluster ID 0;


Or if you just want to free the taken RMI call threads without restart, you can execute the following commands in the AS Java telnet:

- Go to the server process with the hanged thread.

- Execute: "p4_calls" command in P4 command group to list all processing calls. You will see the current p4 call IDs as a result.

- Pick the ID of the p4 call, which hangs;

- Execute: "p4_calls -cancel <P4_Call_ID>"

You have to disable Debug Proxy in order to prevent further hanged calls in cluster-cluster communication.


Or check SAP Note 1800513 2012.
Note: SERVERCORE in 7.30 depends on ENGINEAPI , BASETABLES, J2EE-FRMW.
There are frequently changes in SERVERCORE, which depends on changes in ENGINEAPI, so it is recommended to deploy also dependencies of SERVERCORE, when update SERVERCORE.sca.

Related CSN messages

987504 2012

Related SAP Notes

1800513 2012

  • No labels