SAP Basis Tech Supports

Symptom

Application Server Java (AS Java) stops with exit code -2106.

Other terms

Exit code -2106
P4
P4 port
configuration
System Profile
ServiceConfigurationException

Reason and Prerequisites

In order for the whole AS Java to start, all the services that provide core functionality must be running. If one of the core services cannot be started due to misconfiguration, the Service Manager exits. AS Java cannot operate without any of the core services so it stops with exit code -2106 when a core service is misconfigured.

Solution

Step 1
In the server processes traces, search for ServiceConfigurationException. The traces can be found in:
/usr/sap///j2ee/cluster/server/log/
Step 2
Follow the instructions provided in the exception.
For example:
#2.0#2008 05 19 17:53:30:503#+0300#Error#com.sap.engine.core.service630.container.ServiceRunner#BC-JAS-COR#kernel.sda#001125F52D3900010000000900001BCC#14847350000000002#com.sap.engine.core.service630.container.ServiceRunner#55d0487925b311ddc601001125f52d39##0#Service Runner [p4]#Java#
#Service [p4] error. Nested exception is: [com.sap.engine.frame.ServiceConfigurationException:
P4 core service could not start because of missing or wrong port configuration]#1
#com.sap.engine.frame.ServiceConfigurationException: P4 core service could not start because of missing or wrong port configuration
at_com.sap.engine.services.rmi_p4.server.P4ServiceFrame.start(P4ServiceFrame.java:146)
at_com.sap.engine.core.service630.container.ServiceRunner.startFrame(ServiceRunner.java:155)
at_com.sap.engine.core.service630.container.ServiceRunner.startService(ServiceRunner.java:113)
at_com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:60)
at_com.sap.engine.frame.core.thread.Task.run(Task.java:73)
at_com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:162)
at_com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:260)#
#2.0#2008 05 19 17:53:30:503#+0300#Fatal#com.sap.engine.core.Framework# com.sap.ASJ.krn_frm.000019#BC-JAS-ADM-LOG#kernel.sda#001125F52D3900010000000B00001BCC#14847350000000002#com.sap.engine.core.Framework#55d0487925b311ddc601001125f52d39##0#Service Runner [p4]#Plain#
#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]]#
Step 3 (optional)
If the ServiceConfigurationException is NOT about P4 core service,
and the instructions from the previous step did not help:
* collect the last Data Collector (former Flight Recorder) dumps from /usr/sap//SYS/global/dump folder (where is the name of your instance).
* Archive the content of one of the following folders:
/usr/sap///work
/usr/sap///j2ee/cluster/server/log
Note: If there are more than one server process in your Java Instance, you can provide the logs of all of them, or just the ones that failed to start.
* Report the problem as an customer message for the component that was not able to start and attach the collected dumps and logs.
Note: If you cannot determine the OSS component, use BC-JAS-COR. Your message will be dispatched/moved to the correct component, but this will increase the processing time.

Step 4
If the ServiceConfigurationException is for P4 core service:
“P4 core service could not start because of missing or wrong port configuration” – check configuration in your system profile, then you should know that:
* This exception during P4 core service start means that P4 core service cannot retrieve opened port for RMI-P4 protocol from JStartup and ICM.
* P4 core service cannot start unless ICM opens a port for RMI-P4 communication.
*The most probable reason for the ICM not to be able to open a port for RMI-P4 protocol is a misconfiguration after update or upgrade in the system profile.
* Check official documentation in:
http://help.sap.com/saphelp_nwpi711/helpdata/en/48/3ae05299c172d0e10000000a42189c/frameset.htm
How to solve the misconfiguration issue yourself?
System profile is located in: /usr/sap//SYS/profile/
Open profile in format: __
Note: Profile ending to .1, .2, etc. are backups of previous state of the system profile. They are not used when NetWeaver system starts.
In profile search for key “icm/server_port_”. Something like:
# http port configuration
icm/server_port_0 = PROT=HTTP, PORT=5$(SAPSYSTEM)00, TIMEOUT=600
icm/server_port_1 = PROT=HTTPS, PORT=5$(SAPSYSTEM)01, TIMEOUT=1200
If HTTPS port is configured in configuration slot 1, and there is no configuration for “PROT=P4″ – this is the root cause for the problem.
You may simply add all other ports that you need. For example:
# HTTP port configuration
icm/server_port_0 = PROT=HTTP, PORT=5$(SAPSYSTEM)00, TIMEOUT=600
icm/server_port_1 = PROT=HTTPS, PORT=5$(SAPSYSTEM)01, TIMEOUT=1200
# P4 port configuration
icm/server_port_2 = PROT=P4, PORT=5$(SAPSYSTEM)04
# IIOP/Telnet port configuration
icm/server_port_3 = PROT=IIOP, PORT=5$(SAPSYSTEM)07
icm/server_port_4 = PROT=TELNET, PORT=5$(SAPSYSTEM)08, HOST=localhost
Or
You may correct current configuration, changing HTTPS configuration to a slot, which is not occupied by default values.
Configuration should use consecutive numbers. So we recommend configuring all used protocols in the system profile.
Note: For Double Stack systems you have SMTP port configuration as well

However, if the configuration is correct and still cannot start and exits with Exit Code -2106: Check if configured port is avaialble on machine (not occupied by any other process running).
If the port is not occupied, collect all ERROR logs for ICM and attach the collected information in a customer message to component BC-CST-IC.
Note: ICM logs are located in:
/usr/sap///work/dev_icm
/usr/sap///work/dev_icm.old
You may archive the whole work folder (including dev_icm, dev_icm.old, std_server.out, dev_server, dev_bootstrap, dev_jstart)
Note: You should first ensure, that configuration is correct and configured ports are not occupied by any other processes on the server’s machine.