Solved: Java Engine not running - Server and Dispatcher no...

Former Member · ‎09-14-2010

Hi Gurus,

I am facing a problem starting the Java Stack of one our XI Instance(XI 3.0 on Netweaver 04).The ABAP stack starts up fine but Server and Dispatcher keep on failing to start.It seems that a core service-P4 is failing to start causing the whole issue.We have restarted the Instance,done Cleanipc,restarted the server but nothing helping much.

Logs and Traces:

../work/std_dispatcher.out

SAP J2EE Engine Version 6.40 PatchLevel 100627.313 is starting...

Loading: LogManager ... 683 ms.

Loading: PoolManager ... 6 ms.

Loading: ThreadManager ... 78 ms.

Loading: IpVerificationManager ... 10 ms.

Loading: ConnectionsManipulator ... 28 ms.

Loading: ClassLoaderManager ... 20 ms.

Loading: ClusterManager ... 208 ms.

Loading: PortsManager ... 13 ms.

Loading: LockingManager ... 76 ms.

Loading: ConfigurationManager ... 1440 ms.

Loading: LicensingManager ... 34 ms.

Loading: ServiceManager ...

Loading services.:

Service security started. (11 ms).

Service httptunneling started. (27 ms).

Service sld started. (28 ms).

Service licensing started. (37 ms).

Service r3startup started. (64 ms).

Service timeout started. (59 ms).

Service memory started. (51 ms).

Service webservices started. (32 ms).

Service jmx_notification started. (39 ms).

Service keystore started. (52 ms).

Service shell started. (91 ms).

Service telnet started. (19 ms).

service p4 ================= ERROR =================

Core service p4 failed. J2EE Engine cannot be started.

com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Cannot assign requested address

com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Cannot assign requested address

com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket. at com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor.<init>(TransportMonitor.java:211)

at com.sap.engine.services.rmi_p4.dispatcher.P4ServiceFrame.start(P4ServiceFrame.java:93)

at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:224)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:156)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)

com.sap.engine.frame.ServiceException: <--Localization failed: ResourceBundle='com.sap.engine.frame.KernelResourceBundle', ID='Cannot assign requested address

com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket.', Arguments: []--> : Can't find resource for bundle java.util.PropertyResourceBundle, key Cannot assign requested address

com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor constructor : can't open server socket.

at com.sap.engine.services.rmi_p4.dispatcher.TransportMonitor.<init>(TransportMonitor.java:211)

at com.sap.engine.services.rmi_p4.dispatcher.P4ServiceFrame.start(P4ServiceFrame.java:93)

at com.sap.engine.core.service630.container.ServiceRunner.startCommunicationServiceFrame(ServiceRunner.java:224)

at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:156)

at com.sap.engine.frame.core.thread.Task.run(Task.java:64)

at com.sap.engine.core.thread.impl6.SingleThread.execute(SingleThread.java:78)

at com.sap.engine.core.thread.impl6.SingleThread.run(SingleThread.java:148)

[Framework -> criticalShutdown] Core service p4 failed. J2EE Engine cannot be started.

Sep 14, 2010 6:26:18 AM com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:6]_8] Fatal: Critical shutdown was invoked. Reason is: Core service p4 failed. J2EE Engine cannot be started.

../work/dev_dispatcher

[Thr 37] Tue Sep 14 06:26:18 2010

[Thr 37] JLaunchISetTelnetPort: set telnet port 50308

[Thr 25] JLaunchISetP4Port: set p4 port 50304

[Thr 5] JLaunchIExitJava: exit hook is called (rc=-11113)

../work/dev_jcontrol

**********************************************************************

[Thr 1] JStartupICreateProcess: fork process (pid 2007)

[Thr 1] JControlICheckProcessList: process server0 started (PID:2007)

**********************************************************************

JStartupStartJLaunch: program = /usr/sap/XP1/DVEBMGS03/j2ee/os_libs/jlaunch

-> arg[00] = /usr/sap/XP1/DVEBMGS03/j2ee/os_libs/jlaunch

-> arg[01] = pf=/usr/sap/XP1/SYS/profile/XP1_DVEBMGS03_drvte-db1

-> arg[02] = -DSAPINFO=XP1_03_sdm

-> arg[03] = -file=/usr/sap/XP1/DVEBMGS03/SDM/program/config/sdm_jstartup.properties

-> arg[04] = -nodeName=sdm

-> arg[05] = -nodeId=2

-> arg[06] = -syncSem=64

-> arg[07] = -jvmOutFile=/usr/sap/XP1/DVEBMGS03/work/jvm_sdm.out

-> arg[08] = -stdOutFile=/usr/sap/XP1/DVEBMGS03/work/std_sdm.out

-> arg[09] = -locOutFile=/usr/sap/XP1/DVEBMGS03/work/dev_sdm

-> arg[10] = -mode=JCONTROL

-> arg[11] = pf=/usr/sap/XP1/SYS/profile/XP1_DVEBMGS03_drvte-db1

-> arg[12] = -DSAPSTART=1

-> arg[13] = -DCONNECT_PORT=32866

-> arg[14] = -DLISTEN_PORT=32852

-> arg[15] = -DSAPSYSTEM=03

-> arg[16] = -DSAPSYSTEMNAME=XP1

-> arg[17] = -DSAPMYNAME=drvte-db1_XP1_03

-> arg[18] = -DSAPPROFILE=/usr/sap/XP1/SYS/profile/XP1_DVEBMGS03_drvte-db1

-> arg[19] = -DFRFC_FALLBACK=ON

-> arg[20] = -DFRFC_FALLBACK_HOST=localhost

-> lib path = LD_LIBRARY_PATH=/usr/j2se/jre/lib/sparcv9/server:/usr/j2se/jre/lib/sparcv9:/usr/j2se/jre/../lib/sparcv9:/usr/sap/XP1/DVEBMGS03/j2ee/os_libs:/usr/sap/XP1/SYS/exe/run:/usr/sap/XP1/SYS/exe/runU:/usr/lib:/usr/sap/XP1/DVEBMGS03/j2ee/os_libs:/usr/sap/XP1/DVEBMGS03/j2ee/os_libs:/usr/sap/XP1/SYS/exe/run:/usr/sap/XP1/SYS/exe/runU

-> exe path = PATH=/usr/bin:/usr/sap/XP1/DVEBMGS03/j2ee/os_libs:/oracle/XP1/920_64/bin:/export/home/xp1adm:/usr/sap/XP1/SYS/exe/runU:/usr/sap/XP1/SYS/exe/run:/usr/bin:.:/usr/ccs/bin:/usr/ucb

**********************************************************************

[Thr 1] JStartupICreateProcess: fork process (pid 2008)

[Thr 1] JControlICheckProcessList: process SDM started (PID:2008)

[Thr 1] Tue Sep 14 06:25:53 2010

[Thr 1] JControlICheckProcessList: process dispatcher (pid:2006) died (RUN-FLAG)

[Thr 1] JControlIResetProcess: reset process dispatcher

[Thr 1] JControlIResetProcess: [dispatcher] not running -> increase error count (1)

[Thr 5] SigISetIgnoreAction : SIG_IGN for signal 18

[Thr 5] JLaunchCloseProgram: good bye (exitcode=-11113)

../work/dev_server0

TIME Tue Sep 14 06:26:55 2010

[Thr 139] * RELEASE 640

[Thr 139] * COMPONENT NI (network interface)

[Thr 139] * VERSION 37

[Thr 139] * RC -10

[Thr 139] * MODULE nixxi_r_mt.cpp

[Thr 139] * LINE 8624

[Thr 139] * DETAIL NiPConnect

[Thr 139] * SYSTEM CALL connect

[Thr 139] * ERRNO 146

[Thr 139] * ERRNO TEXT Connection refused

[Thr 139] * COUNTER 2

[Thr 139] *

[Thr 139] *****************************************************************************

[Thr 139] ***LOG Q0I=> NiPConnect: connect (146: Connection refused) [nixxi_r_mt.cpp 8633]

[Thr 139] *** ERROR => GwIConnect: GwConnect to 192.168.208.45 / sapgw01 failed (rc=NIECONN_REFUSED) [gwxx_mt.c 291]

[Thr 139] ***LOG S0T=> GwIConnect, GwConnect (-0010) [gwxx_mt.c 297]

[Thr 139] ***LOG S0R=> GwIConnect, GwConnect () [gwxx_mt.c 302]

[Thr 139] ***LOG S0S=> GwIConnect, GwConnect (sapgw01) [gwxx_mt.c 306]

[Thr 139] ***LOG S90=> SAP_STINIT3, GwIConnect ( 236) [r3cpic_mt.c 1623]

[Thr 139]

*****************************************************************************

*

[Thr 139] * LOCATION CPIC (TCP/IP) on local host with Unicode

[Thr 139] * ERROR partner not reached (host drvte-db1, service sapgw01)

[Thr 139] *

Kindly Help,

Ranjot

desiree_matas · ‎09-16-2010

Hi,

The error:

"Core service p4 failed. J2EE Engine cannot be started. "

This means that the engine tries to open the P4 port on an IP address which does not belong to it or does not exist anymore.

Check the IPs defined at the bindHost property of the p4 service. You can check this in the configtool as follows:

configtool -> Instance -> dispatcher -> services -> p4 -> bindHost

Check the same property under the global dispatcher config too. The IPs defined here must be available and must belong to the host. If you define more IPs here they must be separated by a colon.

On the other hand, also verify if the ip address was missing in the host file. If so, add it and restart the server.

Regards,

Désiré

Former Member · ‎09-16-2010

Hi Desiree,

Thanks a ton.Problem resolved.

Well the problem was an additional IP(backup IP) in bindHost field which was not active.

I removed it and restarted the server.

Thanks again.

Former Member · ‎09-16-2010

Hi all,

Thanks for your replies.

@Vardharajan : The mentioned users are not locked.

@Mohit : I looked into the notes you mentioned particularly 1359784 which was very informative but does not look like any misconfiguration, as no changes have been made to the system(profile,kernel,etc ) recently and the instance was working fine till recently.

@Nelis : No the IP has not been changed or firewall is not blocking this port.

Another important incident which I should mention is that, a few days back due to some problem in the SAN storage all mount points(/sapmnt/<SID>,etc) had gone off, and we had restart the server and all instances running on that. I believe only the JAVA Stack of XI instance didnu2019t came up and other 3 instances came up correctly as well as the ABAP stack of XI instance.

Looking into the logs it seems that core problem is starting the P4 service at port 50304.

I have checked that the port is not busy with any other service.

Most of the core services do start but fails while attempting to start P4 service.

I want to try to run P4 service at a different available free port else than 50304.

Is it OK to do that?

If its Ok then do I only need to make the changes via Configtool only.

Please suggest.

nelis · ‎09-15-2010


com.sap.engine.frame.KernelResourceBundle', ID=Cannot assign requested address

Did you change the ip address of this system ?

Check that the hostname/ip in /etc/hosts match that of the hostname/ip in DNS. Also make sure there is no firewall blocking access to port 50304 on the local system.

Nelis

Former Member · ‎09-15-2010

Hi ,

Please check with Note ::

Note 1359784 - P4 service could not start due to wrong port configuration

Note 948970 - Caller J2EE_GUEST not authorized, only role administrators

It seems that there is some misconfiguration in profile for P4 port .

Thanks..

Mohit

Former Member · ‎09-15-2010

Hi,

JLaunchCloseProgram: good bye (exitcode=-11113)

This happens if the JAVA engine is not able to connect to the UME database. Make sure that the users J2EE_ADMIN, SAPJSF and J2EE_GUEST are not locked in the JAVA client. If these users are locked, unlock them and then try to start the instance once again.

This should resolve ur issue.

Regards,

Varadharajan M

Java Engine not running - Server and Dispatcher not starting up

Accepted Solutions (1)

Accepted Solutions (1)

Answers (5)

Answers (5)

Re: We need help knowing how to edit and improve a...

We need help knowing how to edit and improve an od...

Distribution of fields in the header of the object...

Cross entity BADI for BP Relationships

Re: how to read UI values for BP_REL in derviation...