SAP Knowledge Base Article - Preview

1657881 - J2EE System fails with "exitcode = -1"

Symptom

You find the following message on the dev_jcontrol file:

[Thr  1] *** ERROR => JsfOpenShm: FtInit(SESSION, 2, 192) failed (got (rc = 0 operation successful), expected (rc = 8 already initialized)) [jsfxxshm_mt. 913]
[Thr  1] *** ERROR => Can't create shared memory segment 69 (rc = 1) [jcntrxx_mt.c 1749]
...
[Thr 01] JControlCloseProgram: good bye... (exitcode = -1)
 

This exitcode may also appear when you're experiencing issues with Wily Introscope. In these cases, you can find the following error on the std_server0 file:

Exception in thread "main" java/lang/NoSuchMethodError: java/lang/
ClassLoader.initializeClassLoaders()V
          at java/lang/Thread.initialize (Thread.java:306)
          at java/lang/Thread.<init> (Thread.java:123)
JVMJ9VM015W Initialization error for library jclscar_23(14): JVMJ9VM009E J9VMDllMain failed
</verbosegc>


Read more...

Environment

SAP NetWeaver Application Server Java

Product

SAP NetWeaver 2004 ; SAP NetWeaver 7.0 ; SAP enhancement package 1 for SAP NetWeaver 7.0 ; SAP enhancement package 2 for SAP NetWeaver 7.0 ; SAP enhancement package 3 for SAP NetWeaver 7.0

Keywords

JControl, Startup Framework, shared memory segment, wily, introscope, restart, process, OS, restart, agent
, KBA , BC-JAS-SF , Startup Framework , BC-JAS-COR , Enterprise Runtime, Core J2EE Framework , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.