Skip to Content
2
Former Member
Jul 30, 2015 at 10:45 PM

Pure Java AS 7.40 SP11 J00 won't start after SUM patches and changes applied

107 Views

experts,

We have a AIX-64 bit system that was on NW7.40 SP08 pure JAVA AS with portal.

Previous Kernel:742_REL v17 64-bit unicode

Previous JVM:6.1.046

We updated via SUM SUM10SP13_4 to:

NW7.40 SP11 plus all the one-offs

JVM: 6.1.079

Kernel: 742_REL v212 plus all the one-offs

DB is oracle 11.2.0.4.0 and that version was not changed.

I was told that the SUM was successful ( I didn't do it myself), and then more changes were made:

config tool -

InitialHeapSize was 4096m and changed to 2048m

maxHeapSize was 4096m and changed to 2048m

MaxNewSize was 1365m and changed to 410m

NewSize was 1365m and changed to 410m

And –XX:SurvivorRatio was XXXX and changed to XXXX

KNOW THAT WE BACKED OUT THESE CHANGES LATER...PUT THEM BACK...NO HELP!

in NWA, the HTTP provider service:

CacheControl was 100000 and changed to 604800

SapCacheControl was 100000 and changed to 604800

Finally:

the we added ipc/shm_psize_34=0 to the SCS profile. Previously, that param was not there.

Now the JAVA J00 instance will not start!

The /usr/sap/BID/J00/work/dev_server0 says:

F Main method call:

F com/sap/engine/boot/Start.main()

F ********************************************************************************

J

J Thu Jul 30 16:28:15 2015

J Heap

J par new generation reserved 1397760K, committed 1397760K, used 293580K [0x00000006f0000000, 0x0000000745500000, 0x0000000745500000)

J eden space 1048320K, 28% used [0x00000006f0000000, 0x0000000701eb33c0, 0x000000072ffc0000)

J from space 174720K, 0% used [0x000000072ffc0000, 0x000000072ffc0000, 0x000000073aa60000)

J to space 174720K, 0% used [0x000000073aa60000, 0x000000073aa60000, 0x0000000745500000)

J concurrent mark-sweep generation reserved 2796544K, committed 2796544K, used 2K [0x0000000745500000, 0x00000007f0000000, 0x00000007f0000000)

J Metaspace used 10252K, capacity 10462K, committed 10752K, reserved 272384K

J class space used 1116K, capacity 1178K, committed 1280K, reserved 262144K

F

F [Thr 4113] Thu Jul 30 16:28:15 2015

F [Thr 4113] *** LOG => SfCJavaVm: exit hook is called. (rc = -1501)

F

F ********************************************************************************

F *** ERROR => Java node 'server0' terminated with exit code -1501.

F ***

F *** Please see section 'Java program exit codes'

F *** in SAP Note 1316652 for additional information and trouble shooting advice.

F ********************************************************************************

F

F [Thr 4113] *** LOG => exiting (exitcode -1501, retcode 2).

M [Thr 4113] CCMS: CCMS Monitoring Cleanup finished successfully.

So I did a bunch of note searches which say to look for the "manager log" that will have the real error:

of all the logs, this is the one with a real error:

std_server0.out

ERROR: Cannot read manager properties due to:

java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.boot.FrameThread.initKernelObjects(FrameThread.java:130)

at com.sap.engine.boot.FrameThread.run(FrameThread.java:177)

at com.sap.engine.boot.StartFrame.work(StartFrame.java:93)

at com.sap.engine.boot.Start.main(Start.java:38)

Caused by: java.lang.IllegalArgumentException: The method [resolveCalculatedValue] in the class [com.sap.engine.core.configuration.impl.KernelFriendImpl] cannot be invoked. Check the provided classloader [system:Kernel@com.sap.engine.boot.loader.ResourceMultiParentClassLoader@33c911a1@alive]

at com.sap.engine.bootstrap.online.EvalParser.resolveCalculatedValue(EvalParser.java:162)

at com.sap.engine.bootstrap.online.EvalParser.calculateEvalBasedExpression(EvalParser.java:118)

at com.sap.engine.bootstrap.online.PropertiesHandler.substituteParameters(PropertiesHandler.java:165)

at com.sap.engine.bootstrap.online.Manager.readManagerProperties(Manager.java:271)

... 8 more

Caused by: java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:597)

at com.sap.engine.bootstrap.online.EvalParser.resolveCalculatedValue(EvalParser.java:144)

... 11 more

Caused by: com.sap.engine.lib.lang.expression.MalformedExpressionException: Empty or incomplete expression input []

at com.sap.engine.lib.lang.expression.ExpressionCalculator.evaluate(ExpressionCalculator.java:109)

at com.sap.engine.lib.lang.expression.ExpressionCalculator.calculate(ExpressionCalculator.java:74)

at com.sap.engine.core.configuration.impl.KernelFriendImpl.resolveCalculatedValue(KernelFriendImpl.java:73)

... 16 more

/usr/sap/BID/J00/j2ee/cluster/server0/log default/app logs have nothing new in them.

sappfpar check pf=BID_J00_HOST
sappfpar check pf=BID_SCS01_HOST
BOTH look good!

Notes:
1628335 - J2EE System fails with "exitcode -1501"
--> says can check the std_serverX file, that will contain the faulty manager

1659418 - Java Application Server Exitcodes - Composite KB
--> says "exitcode -1501" means The Java stack fails to start caused by a manager failure

2017999 - AS Java fails to start due to wrong element.clusterID setting
--> says This problem happens due to a wrong setting on the element.clusterID, in the Config Tool.
--> gives instructions on how to resolve in config tool. open the Config Tool and click on "View" and then select "Expert Mode". Now follow the path as in the screenshot
Select the line "element.clusterID" is and make sure the value is ${INSTANCE_ID}50 + ${NODE_INDEX}. Restarting the AS Java is necessary after making the change.
--> but all this seems to be OK when I check it.

MY error log is slightly different than this note!!

Threads:

http://scn.sap.com/thread/1418191

suggests note 723909 but never a real resolution..older version anyway

http://scn.sap.com/thread/3472019

nothing super relevant here

http://scn.sap.com/community/enterprise-portal/blog/2013/06/13/exit-coeds-in-java-stack-and-its-significance

1501 is called a Framework error

http://wiki.scn.sap.com/wiki/display/TechTSG/(JSTTSG)(Kernel)Framework-ExitN1501

search for 1501 some decent trouble shooting...but not relevant for us.

enq looks ok. the /usr/sap/BID/SCS01/work logs appear to be OK.

Did a full stop, full IPC clean...checked sappfpar....log files....

I don't think wily has anything to do with this. doesn't hurt or help at this point. The wily error would only be relevant for say..system copy or fake or something like that.

and would have a whole different error in the dev_server0 and would get farther in the boot up process.

I still think the key is really the /usr/sap/BID/J00/work/std_server0.out but I can't find any further help.

Any suggestions??