cancel
Showing results for 
Search instead for 
Did you mean: 

Java instance not starting after SP09 update

deeraj_shetty
Participant
0 Kudos

Dear Experts,

Java instance not starting after SP09 update on fresh installation of PI 7.31 dual stack.

Support pack SP09 was applied using SUM10 and it was successfully finished.

Post update, ABAP works fine and able to see all the updated SP levels.


Tried below options for fixing this issue:

Increasing/decreasing heap memory and server nodes in config tool and restarted Java server.

Updated Kernel to 721_EXT_REL

Referred below SAP Notes:

1836705 - JNI adoption because of security changes in JVM

1316652 - Analysis of startup errors for the AS Java 7.10


ABAP starts and works fine with updated kernel, but still Java server nodes doesn't start up.


Please Help.


Attaching logs.


Regards,

Deeraj Shetty

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Update your kernel. For more info please read SAP Note 1836705 - JNI adoption because of security changes in JVM

deeraj_shetty
Participant
0 Kudos

Hi Roman,

Thanks for the input. I have referred to the note earlier.

SAP Kernel also updated to 721_EXT_REL. But still facing same issue.

Regards,

Deeraj Shetty

srinivasan_vinayagam
Active Contributor
0 Kudos

Dear Deeraj,

Change Java max heap size values and try to start. And also increase your pagefile memory then restart the OS.

Also check dev_jstart log.

Thanks & Regards,

V Srinivasan

Former Member
0 Kudos

You need to check the patch level of kernel used. Please provide this info here.

deeraj_shetty
Participant
0 Kudos

Hi Srinivasan,

We have high end resource allocated to PI server (Solaris SPARC).

Currently we are having 170GB swap size .

# swap -s

total: 126443192k bytes allocated + 63728608k reserved = 190171800k used, 178317584k available

I have increased heap mem to 4/6 GB, but still same issue .

Regards,

Deeraj Shetty

deeraj_shetty
Participant
0 Kudos

Kernel used : 721_EXT_REL patch number 40

Former Member
0 Kudos

As per note you must have patch level 115 as minimum. Please update your kernel to latest available patch level.

srinivasan_vinayagam
Active Contributor
0 Kudos

Dear Deeraj,

Please share dev_jstart log.

No, you can decrease the heap value.

Regards,

V Srinivasan

Answers (2)

Answers (2)

deeraj_shetty
Participant
0 Kudos

Dear All,

Issue resolved by applying latest patch on kernel as it contained the latest jstart executables.

Updated Kernel patch: 721_EXT_REL patch 201

Helpful SAP Note: 1836705 - JNI adoption because of security changes in JVM


Thank you all for the quick response and support .

Regards,

Deeraj Shetty

former_member235680
Active Participant
0 Kudos

Hi Deeraj,

Below is the error in your logs:

====================================

FATAL: Critical shutdown with exit code [2150] was requested due to [AS Java cannot be started; core service [cross] failed to start]

==================================

Have you seen the below note?

1891477 - PI 7.1X upgrade deployment process fails due to missing ExecutionDetails class

Thanks

Abhi

deeraj_shetty
Participant
0 Kudos

Hi Abhi,

Thanks for the input. Yes I had gone through it and performed below steps:

Re-create the server node from the binaries in the database:

    1) Shut down the whole Java instance.

    2) Rename /usr/sap/<SID>/<Java Instance>/j2ee/cluster/serverX to serverX_old.

    3) Re-start the instance.

But it didn't help.

Note: All the phases in SUM was completed successfully without any errors.

Post SP update, ABAP works fine but Java alone not starting.

Strangely i find below error in one of the dev_w* logs:

A Mon Feb 24 17:21:33 2014

A  UpdateProfile (new settings): off,krn_impl,(no dyn check),(no logging),(no stat err),(local generation),(no commit)

A  UpdateProfile (new exceptions): (tmp_err),(home_err),(local_err)

A  UpdateProfile (new version): 0

A  ***GENER* Trace switched off ***

M  SecAudit(rsauinit): WP attached to existing shared memory.

M  SecAudit(RsauShmInit): addr of SHM for Audit.. = ffffffff5d600000

M  SecAudit(RsauShmInit): addr of RSAUSHM........ = ffffffff5d601000

M  SecAudit(RsauShmInit): addr of RSAUSLOTINFO... = ffffffff5d601610

M  SecAudit(RsauShmInit): addr of RSAUSLOTS...... = ffffffff5d601620

B  dbrda: Redirect database access is disabled via rsdb/rda profile parameter setting.

M Mon Feb 24 17:23:21 2014

M  extStatHook: This process does not report performance statistics

S Mon Feb 24 17:28:21 2014

S  found spool memory service RSPO-ACTIONS at ffffffff44b0b2d8

A Mon Feb 24 17:31:21 2014

A  *** ERROR => RFC ======> Password logon no longer possible - too many failed attempts

[abrfcio.c    9235]

A  {root-id=8010E00B8DC01ED3A7A96C09BD0F0719}_{conn-id=00000000000000000000000000000000}_0

A  *** ERROR => RFC ======> Password logon no longer possible - too many failed attempts

[abrfcio.c    9235]

A  {root-id=8010E00B8DC01ED3A7A96C09BD0F0719}_{conn-id=00000000000000000000000000000000}_0

A Mon Feb 24 17:31:23 2014

*** ERROR => RFC ======> Password logon no longer possible - too many failed attempts

[abrfcio.c    9235]

A  {root-id=8010E00B8DC01ED3A7A96C09BD0F0719}_{conn-id=00000000000000000000000000000000}_0

Any idea which user i need to look for?

Regards,

Deeraj Shetty

Former Member
0 Kudos

Looks like a database user, maybe sapsr3db.
But for further helping you, we first need to know what your database is.

During the upgrade, did you change any database user password?

deeraj_shetty
Participant
0 Kudos

Hi Josef,

Database user is not locked (checked at sql level) and password also not changed during update.

We are using Oracle 11g database.

Am able to login and access configtool without any issue.

Regards,

Deeraj Shetty

Former Member
0 Kudos

Thanks for clarification!
So this user error seems not to be connected to your Java problem.
Btw, those dev_w* are from the ABAP part, aren't they?
In this case please check RFC users in your ABAP system.

As for the Java problem, an SAP notes search with keywords "exit code 2150" will provide severals results, and there are some notes suggesting a kernel upgrade, as also suggested by serveral other repliers here.
Let me join them!

regards