jstart.exe process hanging in "starting the processes"

[Private_Member_742467]

Hello,

I have a JAVA system running on Windows. When trying to start it using SAPMMC the jstart.exe process remains on yellow - Starting the processes for a very long time. It seems like it is hanging. I waited for more than 30 minutes for server0 to start but the status doesn't change.

After checking dev_server0 I found this error:

Option is not recommended for use in productive environments: -XX:+PrintGCTimeStamps
J JVMX version - Feb 20 2020 18:05:32 - 81_REL - optU - windows amd64 - 6 - bas2:318028 (mixed mode)
J Error occurred during initialization of VM
J agent library failed to init: instrument
J [Last 4000 events in the event buffer]
J <thread> <time> <id> <description>
J 13592 0.01 0x00000003 Loaded dll "H:\usr\sap\<SID>\J02\exe\sapjvm_8\jre\bin\instrument.dll" [0x00007ffd9f240000]
J 13592 0.00 0x00000002 Loaded dll "H:\usr\sap\<SID>\J02\exe\sapjvm_8\jre\bin\java.dll" [0x00007ffd98ed0000]

J 13592 0.00 0x00000001 Loaded dll "H:\usr\sap\<SID>\J02\exe\sapjvm_8\jre\bin\verify.dll" [0x00007ffd9f270000]

F
F [Thr 13592] Thu May 28 13:47:29:513 2020
F [Thr 13592] * LOG => SfCJavaVm: abort hook is called.

Looking online for a solution I found some SAP notes related to SPM, but my system is the JAVA stack of Solman 7.2.

Any suggestions on how I might fix this issue and get my JAVA system started?

Thank you.

[former_member643557 · Accepted solution]

hi Gabriel,

it looks like that you got some trouble with your JAVA VM environment

Option is not recommended for use in productive environments: -XX:+PrintGCTimeStamps
J JVMX version - Feb 20 2020 18:05:32 - 81_REL - optU - windows amd64 - 6 - bas2:318028 (mixed mode)
J Error occurred during initialization of VM

The Output with XX:+PrintGCTimeStamps is not harmful, we got the same warning in our dev_server0 output.

Can you paste the output of following command?

"java -version"

1837221 - SAP JVM requires Microsoft Visual C++ 2010 runtime

1367498 - SAP JVM installation prerequisites

On the other hand, is the scs instance running or gots the same failure?

Also you can try to have a look in configtool and check memory for your java servernode.

2599766 - AS Java fails to start - javaagent failed

1857521 - SAP JVM crash due to native memory allocation error

best regards

robert

[Private_Member_742467 · Accepted solution]

The issue was solved by disabling the following parameters in configtools:

-Dcom.wily.introscope.agentProfile
-javaagent
-Dcom.wily.introscope.agent.agentName

Exact steps can be found in SAP Note 2004944.

[Sriram2009]

Hi Gabriel.

1. If possible do the full system restart then try to start the Java instance.

2. If the still same issue pls share the dev_server0 log as attachment

Regards

SS