SAP Note 1158626 - P4 connection to ICM on machine with multiple IPs fails

Component : RMI, P4, CORBA, IIOP - Internet Communication ManagerBC-CST-WDP Web DispatcherHAN-D

Solution : https://service.sap.com/sap/support/notes/1158626 (SAP Service marketplace login required)

Summary :
When using SAP NetWeaver AS Java 7.1 SP5 and above, multiple P4 connections between two VMs on the same network can lead to connection failures or hangs due to simultaneous IP address accessibility on the Internet Communication Manager (ICM). This issue arises if the ICM is configured to listen on all IPs without specific P4 port settings in the instance profile. To resolve this, it is recommended to designate a single IP address for P4 connections in the instance profile by specifying `icm/server_port_N`. This configuration should be applied differently depending on whether all IPs belong to the same network or multiple networks. Changes are effective post system restart. Fixes and patches available from 7.10 SP11 and 7.11 SP6.

Key words :
/usr/sap/<sid>/sys/profile, network_1]icm/server_port_n2 = prot=p4, icm/server_port_n = prot=p4, icm/server_port_n1 = prot=p4, multiple ip addresses accessible, internet communication manager, bco patch level 163, bco patch level 50, sp patch level, choosen  ip address]

Related Notes :

1620345icm/P4/ignore_duplicate_banner does not work
1473530RMI_P4 connectivity problem with EOFException
1389833Deployment to a 7.10 or higher J2EE engine does not work
1351062P4 over multiple IP configured system do not work or fails
1156185Central Note: Upgrade to Systems on SAP NetWeaver 7.1 EHP 1
1061649Upgrade to SAP NetWeaver Process Integration 7.1