JVM Exit code=11

Hello All!
On linux red hat 9 where start IBM WebSphere Studio 5
happend error:
JVM terminated, Exit code=11
Where I find documentation about it?
With best regards,
Valery Bondarenko

can you help me in this:
i need a code [how to exit in java programing-in MS.DOS.
Thanks..
SAMIS

Similar Messages

Eclipse failing to start - JVM Exit code 1

Hello
Apologies if this issue has already been posted.
I am seeing that my Eclipse IDE is crashing everytime I try to start it, with JVM exit code 1.
FYI, my version of java is:
$java -version
java version "1.5.0_12"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_12-b04)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_12-b04, mixed mode)
I am running it on openSuse 10.3 x86_64.
The error I get is:
JVM terminated. Exit code=1
/usr/bin/java
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx256m
-jar /home/suman/downloads/test/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-os linux
-ws gtk
-arch x86_64
-showsplash
-launcher /home/suman/downloads/test/eclipse/eclipse
-name Eclipse
--launcher.library /home/suman/downloads/test/eclipse/plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.0.3.R33x_v20080118/eclipse_1023.so
-startup /home/suman/downloads/test/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
-exitdata 348015
-vm /usr/bin/java
-vmargs
-Dosgi.requiredJavaVersion=1.5
-Xms40m
-Xmx256m
-jar /home/suman/downloads/test/eclipse/plugins/org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
Any help would be much appreciated.
Thanks
Debz.

Thanks.
But I was wondering what is JVM EXit Code 1 ? Hoping its not something to do with CLASSPATH settings or anything like that.
Rgds
Debz.

Jvm exit code 128

I'm running a memory / cpu and thread intensive program that's using JIntegra for a com bridge. We're hammering our windows 2003 server machine with 4 gigs of ram pretty hard.
We're also using the java service wrapper to launch our java process. Under this heavy load I see this:
JVM process exited with a code of 128, setting the wrapper exit code to 128.
What is this exit code telling me?

test reply
Edited by: lhyang on Jun 3, 2008 3:30 PM

JVM, exit codes and Windows 98

Has anyone got System.exit(integer) to return a value other than 0 under Windows 98?
Regardless of what integer I enter as an exit code, java.exe always seems to return 0. This does not seem to be the case under Windows NT, where the correct exit code is passed back.
Is anyone aware of this problem/found a workaround?

How are you checking the exit value under 98?

JVM terminated exit code = ...

When using wsad 5, and trying to start the server I obtain an error :
JVM terminated exit code = -1073741819 E:\...\javaw.exe
-cp E:\...\startup.jar org.eclipse.core.launcher.Main
-oswin32
-wswin32
-arch x86
-showsplash e:\...\eclipse.exe
-showsplash 600 de programa\wsad\.\eclipse\eclipse.exe
-data E:\...\workspace
where can I find the meaning of JVM exit codes? or Does anybody knows what does this one means?
thanks

You might need to run Eclipse properly
All arguments following (but not including) the -vmargs entry are passed directly through to the indicated Java VM as virtual machine arguments (that is, before the class to run). Note: If an Eclipse startup argument, such as -data, is provided after the Java vm arguments (-vmargs), Eclipse will not start and you will receive a "JVM terminated. Exit code=1" error.
Running on Different VMs
Running Eclipse on J9
When running Eclipse on J9 version 1.5, it is recommended that you use the following VM options:
eclipse.exe [eclipse arguments] -vm path_to_j9w.exe
-vmargs -ms:32 -mm:2048 -mo:32768 -moi:32768 -mca:32 -mco:128 -mx:2000000
When running Eclipse on J9 version 2.0, the default arguments chosen by J9W should be suitable. However, to override the parameters which are automatically set internally by the Eclipse executable, you must specify -vmargs with no following arguments as follows:
eclipse.exe [eclipse arguments] -vm path_to_j9w.exe -vmargs
Please refer to the J9 VM documentation and help for further information.
Running Eclipse on the IBM Developer Kit, Java(TM) Technology Edition VM
The default VM settings for IBM Developer Kit, Java(TM) Technology Edition 1.3 Linux work well for initial exploration, but are not sufficient for large scale development. For large scale development you should modify your VM arguments to make more heap available. For example, the following setting will allow the Java heap to grow to 256MB:
-vmargs -Xmx256M
for more details
http://dev.eclipse.org/viewcvs/index.cgi/~checkout~/org.eclipse.platform.doc.user/tasks/running_eclipse.htm

Runtime.getRuntime().exec(...) problems and exit codes

Hi,
I am trying to launch an application 4 times with different arguments from a Java app. I have tried doing it sequentially and in four different threads, but the results are the same: sometimes the 4 of them are properly launched, sometimes (the most of the times) only 3 are launched and sometimes only 2. I have tried with cmd and cmdarray[] as parameters for exec but the results are the same.
This is one of the four threads I use:
Runnable r1 = new Runnable(){
                    public void run(){
                         String ecgCommand = "./flute -S -m:" + Config.ECGS_FLUTE_IP + " -p:" + Config.ECGS_FLUTE_PORT + " -F:" + Config.ECGS + " -r:" + Config.ECGS_FLUTE_RATE + " -C";
                         System.out.println(ecgCommand);
                         InputStream ecgsStream = null;
                         InputStreamReader isr = null;
                         BufferedReader br = null;
                         try{
                              ecgsProcess = Runtime.getRuntime().exec(ecgCommand, null, new File(Config.HOME_PATH + Config.FLUTE_PATH));
                              String line;
                              ecgsStream = ecgsProcess.getInputStream();
                              isr = new InputStreamReader(ecgsStream);
                              br = new BufferedReader(isr);
                              StyledDocument styleDoc = mm.ecgFluteMessages.getStyledDocument();
                              Style def = StyleContext.getDefaultStyleContext().getStyle(StyleContext.DEFAULT_STYLE);
                              while((line = br.readLine()) != null && running){
                                   if(styleDoc.getLength() > 25000)     mm.ecgFluteMessages.setText("");
                                   styleDoc.insertString(styleDoc.getLength(), line+ "\n", def);
                                   mm.ecgFluteMessages.setCaretPosition(mm.ecgFluteMessages.getDocument().getLength());
                              System.out.println(ecgsProcess.waitFor());
                         }catch(Exception e){
                              try {
                                   br.close();
                                   isr.close();
                                   ecgsStream.close();
                              } catch (Exception e1) {
                                   e.printStackTrace();
               new Thread(r1).start();Adding a Thread.sleep between runnables doesn't have any effect.
In addition, those processes that are not properly launched return an exit value of 255. I have searched for its meaning but I have found nothing. Could anybody tell me where can I find a list of the JVM exit codes in order to guess what is happening?
Can anybody help me with this issue? Help is much appreciated.
Thanks a lot

I have been looking for it but it seems it has not any exit code list or any documentation regarding this. Anyway, I think 255 is a JVM error code (the last one, errors are numbered in modulo 256) which means that the error has nothing to do with JVM but with the application execution (flute in my case).
I have added a prompt for the errorStream and I have this message for the 255 exited programs:
not well-formed (invalid token) at line 15+
And the four commands are like this:
*./flute -S -m:239.255.255.253 -p:60102 -F:./ecgs -r:150 -C*
*./flute -S -m:239.255.255.252 -p:60103 -F:./ads -r:150 -C*
*./flute -S -m:239.255.255.251 -p:60104 -F:./pushvod -r:50 -C*
*./flute -S -m:239.255.255.250 -p:60105 -F:./banners -r:150 -C*
So, as the process is sometimes initialized properly and others it is not, it seems that there is a problem with the tokenizing of the command not happening always. As I have tried it with a single command line and with an array of command strings (the first for "./flute" and the followings for each argument) with the same results I can't understand why is this problem happening sometimes. Happening always would help me in giving a clue but that's not the case.
Any idea? Thanks a lot.
Edited by: dulceangustia on Apr 3, 2008 3:41 AM

How can a JVM terminate with an exit code of 141 and no other diagnostics?

Hello,
We are encountering a JVM process that dies with little explanation other than an exit code of 141. No hotspot error file (hs_err_*) or crash dump. To date, the process runs anywhere from 30 minutes to 8 days before the problem occurs. The last application log entry is always the report of a lost SSL connection, the result of an thrown SSLException. (The exception itself is unavailable at this time – the JVM dies before it is logged -- working on that.)
How can a JVM produce an exit code of 141, and nothing else? Can anyone suggest ideas for capturing additional diagnostic information? Any help would be greatly appreciated! Environment and efforts to date are described below.
Thanks,
-KK
Host machine: 8x Xeon server with 256GB memory, RHEL 6 (or RHEL 5.5) 64-bit
Java: Oracle Java SE 7u21 (or 6u26)
java version "1.7.0_21"
Java(TM) SE Runtime Environment (build 1.7.0_21-b11)
Java HotSpot(TM) 64-Bit Server VM (build 23.21-b01, mixed mode)
JVM arguments:
-XX:+UseConcMarkSweepGC
-XX:+CMSIncrementalMode
-XX:+CMSClassUnloadingEnabled
-XX:MaxPermSize=256m
-XX:NewSize=64m
-Xms128m
-Xmx1037959168
-Djava.awt.headless=true
-Djava.security.egd=file:///dev/./urandom
Diagnostics attempted to date:
LD_PRELOAD=libjsig.so.   A modified version of libjsig.so was created to report all signal handler registrations and to report SIGPIPE signals received. (Exit code 141 could be interpreted as 128+SIGPIPE(13).) No JNI libraries are registering any signal handlers, and no SIGPIPE signal is reported by the library for the duration of the JVM run. Calls to ::exit() are also intercepted and reported. No call to exit() is reported.
Inspect /var/log/messages for any indication that the OS killed the process, e.g. via the Out Of Memory (OOM) Killer. Nothing found.
Set ‘ulimit –c unlimited’, in case the default limit of 0 (zero) was preventing a core file from being written. Still no core dump.
‘top’ reports the VIRT size of the process can grow to 20GB or more in a matter of hours, which is unusual compared to other JVM processes. The RES (resident set size) does not grow beyond about 375MB, however, which is an considered normal.
This JVM process creates many short-lived Thread objects by way of a thread pool, averaging 1 thread every 2 seconds, and these objects end up referenced only by a Weak reference.   The CMS collector seems lazy about collecting these, and upwards of 2000 Thread objects have been seen (in heap dumps) held only by Weak references. (The Java heap averages about 100MB, so the collector is not under any pressure.) However, a forced collection (via jconsole) cleans out the Thread objects as expected. Any relationship of this to the VIRT size or the JVM disappearance, however, cannot be established.
The process also uses NIO and direct buffers, and maintains a DirectByteBuffer cache. There is some DirectByteBuffer churn. MBeans report stats like:
Direct buffer pool: allocated=669 (20,824,064 bytes), released=665 (20,725,760), active=4 (98,304) [note: equals 2x 32K buffers and 2x 16K buffers]
java.nio.BufferPool > direct: Count=18, MemoryUsed=1343568, TotalCapacity=1343568
These numbers appear normal and also do not seem to correlate with the VIRT size or the JVM disappearance.

True, but the JNI call would still be reported by the LD_PRELOAD intercept, unless the native code could somehow circumvent that. Using a test similar to GoodbyeWorld (shown below), I verified that the JNI call to exit() is reported. In the failure case, no call to exit() is reported.
Can an OS (or a manual) 'kill' specify an exit code? Where could "141" be coming from?
Thanks,
-K2
=== GoodbyeWorldFromJNI.java ===
package com.attachmate.test;
public class GoodbyeWorldFromJNI
    public static final String LIBRARY_NAME = "goodbye";
    static {
        try {
            System.loadLibrary(LIBRARY_NAME);
        } catch (UnsatisfiedLinkError error) {
            System.err.println("Failed to load " + System.mapLibraryName(LIBRARY_NAME));
    private static native void callExit(int exitCode);
    public static void main(String[] args) {
        callExit(141);
=== goodbye.c ===
#include <stdlib.h>
#include "goodbye.h" // javah generated header file
JNIEXPORT void JNICALL Java_com_attachmate_test_GoodbyeWorldFromJNI_callExit
(JNIEnv *env, jclass theClass, jint exitCode)
    exit(exitCode);
=== script.sh ===
#!/bin/bash -v
uname -a
export PATH=/opt/jre1.7.0_25/bin:$PATH
java -version
pwd
LD_PRELOAD=./lib/linux-amd64/libjsigdebug.so java -classpath classes -Djava.library.path=lib/linux-amd64 com.attachmate.test.GoodbyeWorldFromJNI > stdout.txt
echo $?
tail stdout.txt
=== script output ===
[keithk@keithk-RHEL5-dev goodbyeJNI]$ ./script.sh
#!/bin/bash -v
uname -a
Linux keithk-RHEL5-dev 2.6.18-164.2.1.el5 #1 SMP Mon Sep 21 04:37:42 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux
export PATH=/opt/jre1.7.0_25/bin:$PATH
java -version
java version "1.7.0_25"
Java(TM) SE Runtime Environment (build 1.7.0_25-b15)
Java HotSpot(TM) 64-Bit Server VM (build 23.25-b01, mixed mode)
pwd
/tmp/goodbyeJNI
LD_PRELOAD=./lib/linux-amd64/libjsigdebug.so java -classpath classes -Djava.library.path=lib/linux-amd64 com.attachmate.test.GoodbyeWorldFromJNI > stdout.txt
echo $?
141
tail stdout.txt
JSIG: exit(141) called
JSIG: Call stack has 4 frames:
JSIG: ./lib/linux-amd64/libjsigdebug.so [0x2b07dc1bdc2f]
JSIG: ./lib/linux-amd64/libjsigdebug.so(exit+0x29) [0x2b07dc1bea41]
JSIG: /tmp/goodbyeJNI/lib/linux-amd64/libgoodbye.so [0x2aaab3e82547]
JSIG: [0x2aaaab366d8e]
=== ===

RCP application on Windows JVM 1.6.0_12 crashed with exit code = 1073807364

A user was using my RCP-based application over several days. At one point, when he apparently wasn't actively using it, the JVM crashed with exit code 1073807364. After some research, I haven't been able to determine what this exit code refers to.
On additional, possibly helpful bit of information is that the hex equivalent 0x40010004 is used to indicate Windows task status. However, this app is not running Windows tasks that I know of, although perhaps RCP, SWT or the SQL Server JDBC layer is doing so without my knowledge.
Can anyone tell me what this exit code indicates, or how to find out?

[http://java.sun.com/javase/6/webnotes/trouble/TSG-VM/html/crashes.html]

Error code 143 on JVM exit

Hello,
I have a program (with multiple threads, running under MS-Windows) which works fine almost all the time.
In one case, it terminated unexpectedly, and the exit code (via ERRORLEVEL) is 143.
There are no other outputs in order to diagnose the problem.
I would like to know what the error code 143 exactly means.
Can anybody give me an advice?
Regards,
Sabrina Werscheid

Hello!
I hope people there is reading old posts too. I have the same problem with code 143. JVM exits unexpectedly, but I believe it is specific block of code which acts differently. I`m trying solution with -Xrs switch, but I`m sure I have no JNI and there is no System.exit() in code at all. Also I know there is no external processes which asks JVM to close.
I have running special FIT tests in child-jvm as ANT task. The exiting is ANT task, not my FIT tests, but at the same time this is not happening on any other processes.
I can`t found any references about "Internal field must be valid". What does it mean? What and where to search for problem?
Any other ideas?
Using JVM 1.5.14

Netweaver Developer Studio 7.3 "JVM terminated exit code = -1"

Hello,
the developer studio can not be started and the error which is shown is "jvm terminated. exit code = -1"
My system is windows7, I am using oracle java 1.6, NWDS (7.3 SP01).
This is my .ini file:
-vm
C:\Program Files\Java\jdk1.6.0_21\bin\
-startup
plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715.jar
-nl
en
-vmargs
-Xmx512m
-Xms128m
-XX:PermSize=32m
-XX:MaxPermSize=256m
-Dfile.encoding=UTF-8
-XX:+HeapDumpOnOutOfMemoryError
-Dosgi.requiredJavaVersion=1.6
Very strangely, I actually succedeed to run the NWDS once when saving the .ini as unicode. But then I could not update the studio with new features, I got "Unsupported major.minor version 49.0u2033. I suspect that actually the studio could not be started properly with java 1.6, but with java 1.4, which was also installed on my system. After deinstalling java 1.4.2, the studio can not be started again.
Please, help me to resolve it.

I resolved the problem. The NWDS required 32-bit JVM and I used 64-bit.
The interesting thing is that java -version says:
Error loading: C:\Program Files (x86)\Java\jre6\bin\msvcr71.dll
Error occurred during initialization of VM
Unable to load native library: Can't load IA 32-bit .dll on a AMD 64-bit platform

Exit code 143 from JVM

Hello
We have an application that is spawned by a windows batch file. We are using JDK 1.5 update 10 on Windows 64 bit AMD platform.
While the program is running we see it abruptly exit with an exit code of 143. There are no exceptions - nothing at all.
What could be the possible causes for this?
Thanks
-giriraj

When I see this it's because the JVM received CTRL_SHUTDOWN_EVENT, and exits with code 143; Obviously I see this when the system is shutting down. See this page:
[http://www.ibm.com/developerworks/java/library/i-signalhandling/]
I assume different events, such as CTRL_LOGOFF_EVENT will also terminate the JVM with an exit code, which might also be 143. However, when I use the Task Manager to kill the Java process, I get an exit code of 1.

Maven - ERROR: Maven JVM terminated unexpectedly with exit code 0

Hi All,
I have written pom.xml for auto deployment process between hudson and deployment servers.
The script which i return its working perfectly i can see the application in web logic server. The application has been deployed in the web logic server. No issues that.
All the remaining task is also very well working in the servers but the build is failing as **failed** by saying the below error in hudson
[ServerConnectionImpl.close():332] : Closing DM connection
[ServerConnectionImpl.close():352] : Unregistered all listeners
[ServerConnectionImpl.closeJMX():372] : Closed JMX connection
[ServerConnectionImpl.closeJMX():384] : Closed Runtime JMX connection
[ServerConnectionImpl.closeJMX():396] : Closed Edit JMX connection
**ERROR: Maven JVM terminated unexpectedly with exit code 0**
Sending e-mails to: [email protected]
Finished: FAILURE
I dont why like this happening in the maven.
Here is my maven opts set in Hudson server.
Maven_OPTS : -Xms256m -Xmx1024m -XX:MaxPermSize=512m
kindly help me to resolve this issue. Thanks in advance.
Regards,
Rocky.

Hi Sir,
Please try the following items:
1. if ther is anti-virus installed , please uninstall it temporarily
2. run " sfc /scannow "
3. keep windows up-to-date
4. if you updated some hardware driver please roll it back
5. if the issue persists , please use windows installation media to perform inplace-upgrade for the system
Also please refer to reinstall C++ runtime within the similar thread:
https://social.technet.microsoft.com/Forums/windows/en-US/bf69eeff-24c4-499f-b280-b6a3098f4f9f/problem-with-msvcrtdll-version-70760117744?forum=w7itprogeneral
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

NWDS NW 7.0 EHP2 with SAP JVM 4.1 == server0 crash exit code 666

I recently installed developer workplace on windows 2003 server SP2, database MS SQL 2005.
NWDS NW 7.0 EHP2. The installation has been done with SUN JAVA kit. The installed SAP AS JAVA was running OK.
Several SAP notes indicate that from NW 7.0 customers should switch to SAP JVM. I have switches from SUN to SAP JVM using the switch tool. From that moment on, me server0 keeps on restarting (19 restart) before it finally stops with exit code 666. The log shows out-of-memory. I have checked note 1522200 and 1603093 (and some others)
Who can help? Has someone this version running in win 2003? I would like to compare the JVM parameters in that case.

We found a solution. We installed SP02 of NW 7.0 EHP2 from DVD. After upgrading to SP08 with JSPM the problems were gone. Parameter settings in the switch tool (according to the mentioned sap notes) are correct.
Wilbert Karremans

Workspace for Weblogic 10gR3 keep hanging JVM terminated. Exit code=107380

Hi,
My workpace 10gR3 IDE sometime will hang when I was coding half way. The cause of it occurrence is always different.
When I force shut down the workspace, the following error is display.
JVM terminated. Exit code=1073807364
D:/bea103/jrockit_160_05/jre/bin/javaw.exe
-Xms768
-Xmx1024m
-XX:MaxPermSize=256m
-XX:PermSize=192m
-XX:NewRatio=3
-Xss256k
-DprodMode=production
-Dweblogic.home=D:/bea103/wlserver_10.3
-Dsun.lang.ClassLoader.allowArraySyntax=true
The workspace is running on Windows XP 32 bits OS.
Can someone assist me to resolve this problem.
Thank you.
Edited by: 957598 on Sep 7, 2012 1:13 AM

Anybody has a similar problem ?
Or is there anyone has experience hang on the IDE?
Thank you

New ALSB3.0 install, WorkSpaceStudio "JVM terminated. Exit code=127"

I'm trying to get ALSB up and running on Oracle Enterprise Linux 5.2 32-bit. I have it installed and the QuickStart will start up. However, when try to launch WorkSpaceStudio I receive the following error:
JVM terminated. Exit code=127
/root/bea/jdk150_11/jre/bin/java
-Xms384m
-Xmx768m
-XX:MaxPermSize=256m
-XX:PermSize=192m
-XX:NewRatio=3
-Xss256k
-Dweblogic.home=/root/bea/wlserver_10.0
-Dosgi.install.area=/root/bea/tools/eclipse_pkgs/1.1/eclipse_3.2.2/eclipse
-Dosgi.instance.area.default=/root/bea/user_projects/workspaces/workSpaceStudio
-Dosgi.configuration.area=/root/bea/workSpaceStudio_1.1/workSpaceStudio/eclipse/configuration
-Declipse.product=com.bea.workspacestudio.product.workspacestudio
-Dosgi.splashPath=file:/root/bea/workSpaceStudio_1.1/workSpaceStudio/eclipse/plugins/com.bea.workspacestudio.product
-jar /root/bea/workSpaceStudio_1.1/workSpaceStudio/startup.jar
-os linux
-ws gtk
-arch x86
-launcher /root/bea/workSpaceStudio_1.1/workSpaceStudio/workSpaceStudio
-name WorkSpaceStudio
-showsplash 600
-exitdata 32000a
-vm /root/bea/jdk150_11/jre/bin/java
-vmargs
-Xms384m
-Xmx768m
I did set up the environment variables located in WLHOME/server/bin/ This error appears to be an environment issue. Is there something else I need to do other than the setWLSEnv.sh script?
Cheers,
Scott

I resolved this issue. It is an Eclipse problem when loading WorkSpace Studio. The exact fix is to set an environment variable prior to launching Quick Start or WorkSpace Studio. Fix listed below:
# export MOZILLA_FIVE_HOME=""

JVM Exit code=11

Similar Messages

Maybe you are looking for