Symptom
During upgrade from Solution Manager 7.1 (SAP NetWeaver 7.0 basis) to Solution Manager 7.2 (SAP NetWeaver 7.4 basis) the Java server P4 service startup fails.
The /usr/sap/<SID>/<inst_nr>/work/std_server0.out file contains the following log entries:
Service [p4] start ================= ERROR =================
CSN Component [BC-JAS-COR-RMT], DC Name [sap.com/p4]
com.sap.engine.frame.ServiceConfigurationException: P4 core service could not start because of missing or wrong port configuration.
Check ICM configuration and logs.
Check that configured (or default) port for RMI-P4 protocol is not occupied.
at com.sap.engine.services.rmi_p4.server.P4ServiceFrame.start(P4ServiceFrame.java:200)
at com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:165)
at com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:118)
at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:65)
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)
FATAL: Critical shutdown with exit code [-2106] was requested due to [AS Java cannot be started;
core service [p4] failed to start because of incorrect configuration [P4 core service could not start because of missing or wrong port configuration.
Check ICM configuration and logs. Check that configured (or default) port for RMI-P4 protocol is not occupied. ]]
Read more...
Environment
SAP NetWeaver 7.4
Solution Manager 7.2
Product
Keywords
P4 service, startup, ICM , KBA , BC-JAS-SF , Startup Framework , BC-JAS-COR-RMT , RMI, P4, CORBA, IIOP , 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.