START_J2EE_INITIAL - java unable to start

[v_veeramalla]

Hi All,

   We are upgrading ECC5.0 system to ECC6.0 EHP1, and we are using sapup and sapjup to perform this activity.

We are in the downtime phase and ABAP is at phase GETSYNC_MODPROF_FINISH and waiting for java.Java is in phase "START_J2EE_INITIAL" and failing with error.

Tried to start manully also

/usr/sap/jupgrade/exe/jcontrol -DSAPSTART=1 pf=/usr/sap/SID/SYS/profile/SID_DVEBMGS00_<hostname>

When i try to check jcontrol log found the error

WARNING => Can't attach to message server (<HOSTNAME>/3901) [rc = -10]-> reconnect [jcntrms_mt.c 371]

[Thr 139791212267264] Wed Nov 13 11:43:26 2013

[Thr 139791212267264] ***LOG Q0I=> NiIWrite: 10.63.15.10:3901: writev (32: Broken pipe) [nixxi.cpp 4603]

[Thr 139791212267264] *** ERROR => NiIWrite: SiSendV failed for hdl 30/sock 9

    (SI_ECONN_BROKEN/32; UD; ST; 10.63.15.10:3901) [nixxi.cpp    4603]

[Thr 139791212267264] *** ERROR => MsINiWrite: NiBufSend (rc=NIECONN_BROKEN) [msxxi_mt.c   2779]

[Thr 139791212267264] *** ERROR => MsIDetach: MsINiWrite (rc=MSENILAYER) [msxxi_mt.c   1302]

I checked the profile

1. SCS

rdisp/msserv = 0

rdisp/msserv_internal = 3901  //initially it was 0 changed to 390

2. Default

j2ee/ms/port = 3901  //added this one

rdisp/msserv = 3602

3. Instance j2ee/ms/port - 3901 //initially it was 0 changed to 3901

configtool message server port is initially 3600 and changed to 3901 as per sap note 1623885

staill we are getting same issue.

Please help us to resolve this issue.

//Veeramalla

j2ee/ms/port           

[v_veeramalla · Accepted solution]

Issue was resolved , having two issues.

updated the kernel files in all locations like (instance exe ...) and second issue is profile parameters

1. SCS

rdisp/msserv = 0

rdisp/msserv_internal = 3901  //initially it was 0 changed to 390

2. Default

j2ee/ms/port = 3901  //added this one

rdisp/msserv = 3602

[Reagan]

Stop SAP and restart the system after cleaning the shared memory segments

Post the trace files dev_w0 and dev_ms

Regards

RB

[Former Member]

Hi,

Please also past the be the below logs.

 ABAP is at phase GETSYNC_MODPROF_FINISH and waiting for java.Java is in phase "START_J2EE_INITIAL"

/usr/sap/<SID>/<instance>/work/std_server0.out

This should give the exact info why the java is not coming up.

Hope that the database is running test R3trans -d.

When you restarted hope you cleared all the hanging processes so that port is still not used by any other process.

Just check the below note alos.

1645418 - SUM: Upgrade stops on START_J2EE_INITIAL phase

Thanks

Rishi Abrol

[v_veeramalla]

I did the restart couple of times , but still same issue.

As of now , instance 02 (actual instance 00) is up and running(ABAP).

//Venkat

[v_veeramalla]

Hi Rishi,

  i did the restart and cleaned up shared every time i restart. R3trans -d is giving return code 0000 which means success.

   Server0 is not coming up , it's failing with jcontrol it self .

ARNING => Can't attach to message server (<HOSTNAME>/3901) [rc = -10]-> reconnect [jcntrms_mt.c 371]

[Thr 139791212267264] Wed Nov 13 11:43:26 2013

[Thr 139791212267264] ***LOG Q0I=> NiIWrite: 10.63.15.10:3901: writev (32: Broken pipe) [nixxi.cpp 4603]

[Thr 139791212267264] *** ERROR => NiIWrite: SiSendV failed for hdl 30/sock 9

    (SI_ECONN_BROKEN/32; UD; ST; 10.63.15.10:3901) [nixxi.cpp    4603]

[Thr 139791212267264] *** ERROR => MsINiWrite: NiBufSend (rc=NIECONN_BROKEN) [msxxi_mt.c   2779]

[Thr 139791212267264] *** ERROR => MsIDetach: MsINiWrite (rc=MSENILAYER) [msxxi_mt.c   1302]

  Since ABAP is phase "GETSYNC_MODPROF_FINISH" , instance 02(actual instance is 00) is up and running and i can see startporofile of instnace two only .

//Venkat

[Former Member]

Hi,

can you please pass on the logs as requested in the earlier blog.

/usr/sap/<SID>/<instance>/work/std_server0.out

Thanks

Rishi abrol

[former_member185239]

Hi Veera,

In the work directory , check the bootsrap logs.

In bootstrap logs you need to check whether it is able to connect the database or not.

If it is ok.

Then check the dev_server0 and server0.out log files.

With Regards

Ashutosh Chaturvedi

+919818619396

[Nibu]

Please check  and post java related logs , like jvm_bootstrap.out , dev_bootstrap etc in work directory . You may get some clue .  And I would suggest to clear the shared memory , kill the processes if anything related is active before starting the system .I had such an issue, which was with the jdbc driver j2ee/dbdriver  parameter in instance profile  was wrong .

Regards,

Nibu Antony