NoClassDefFoundError after System.exit() is called.

I have found a strange condition with JDK 1.4.2_05 and could not find a bug which relates to it.
I have multiple threads running, when I shutdown, I call all the threads to shutdown and finally in main I call System.exit(0).
The strange thing is that one shutdown I get a NoClassDefFoundError for a class which will load fine if loaded before shutting down.
This occurs as the class in question is only needed to perform a shutdown, and in fact the attempt to load it comes after the main thread has finished.
The workaround has been to create an instance of the class when the application is started rather than during shutdown.
Does anyone seen this behaviour?

java.lang.NoClassDefFoundError: com/cantor/framework/run/impl/ShutdownRMB
     at com.can.framework.run.RunnerManagerBean.shutdown(RunnerManagerBean.java:147)
     at com.can.framework.layer.VanillaBean.shutdown(VanillaBean.java:278)
     at com.can.main.Main.main(Main.java:135)
     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:324)
     at com.intellij.rt.execution.application.AppMain.main(AppMain.java:78)

Similar Messages

Why in COM, set smth true, stays true even after System.exit?

I am using "Jacob" to do COM calls. When I alter the "ShowAll" property of Word.Application and I set it to true, it will then forever be true even if I exit the application AND quit the word application. If I set it to false, the same thing happens, it will always be so. The code to call/set this is:
(NOTE: This uses classes I made to wrap the Dispatch calls)
Word wordApp = new Word();
Documents docs = wordApp.getDocuments();
Document doc = docs.open("D:\\JavaProjects\\Test.doc");
//GET VIEW
View wordView = wordApp.getActiveWindow().getView();
//PRINT THE VIEW PROPERTIES
System.out.println("Show All: " + wordApp.getActiveWindow().getView().isShowAll());
System.out.println("Show Paragraphs: " + wordApp.getActiveWindow().getView().isShowParagraphs());
//SET THE VIEW PROPERTIES
wordView.setShowAll(false);
wordView.setShowParagraphs(true);
//PRINT THEM AGAIN
System.out.println("Show All: " + wordApp.getActiveWindow().getView().isShowAll());
System.out.println("Show Paragraphs: " + wordApp.getActiveWindow().getView().isShowParagraphs());
doc.close(Document.DO_NOT_SAVE);
wordApp.quit(new Variant[] {});
System.exit(0);The actual Dispatch calls are:
//NO IDEA WHY THIS IS, BUT SHOWALL = TRUE IS -1, AND FALSE IS 0
private final static int SHOW_ALL_TRUE = -1;
private final static int SHOW_ALL_FALSE = 0;
/** SETSHOWPARAGRAPHS **
* Sets the property (boolean) ShowParagraphs.
public void setShowParagraphs(boolean showParagraphs)
 Dispatch.put(this, "ShowParagraphs", new Boolean(showParagraphs));
/** ISSHOWPARAGRAPHS **
* Returns Boolean of whether or not this is set to show paragraphs.
public boolean isShowParagraphs()
 return getBooleanValue(Dispatch.get(this, "ShowParagraphs"));
private boolean getBooleanValue(Variant variantBoolean)
 //MAKE IT AN INTEGER AND GET ITS int VALUE
 int intVariant = new Integer(variantBoolean.toString()).intValue();
 //RETURN IF IS SHOW ALL
 return (intVariant == View.SHOW_ALL_TRUE);
}I'm wondering if the problem is that I get back either -1 or 0 and if maybe that means something else?

1: Properties persistence is not a DEFECT but a FEATURE . It was implemented in MS Word so users could change MS word WITHOUT HAVING TO DO IT EACH TIME THEY START IT UP.
2: Don't you intialise all your variables in your code after you instanciated them ? I am sure you do so and therefore the persitence feature you described should not be annoying you at all. It is not necessary to intialise variables in the BASIC langage but that does not mean you should not do it.
3: (-1) was chosen arbitrary by Microsoft as the TRUE value for Boolean datatype and 0 the value for FALSE when they designed Visual Basic. This is not a problem if you write code properly
I recommend you test bool variable in any langages using the following test:
(myBool <> 0)
HAVE A THINK ABOUT IT
Finally,
you need to understand what you are working with before you complain about it.
Argument for Argument sake is not good and if you think MS word is a bad program just don't use it. go and write your own word processor in JAVA.
GOOD LUCK
I WISH TO APOLOGISE FOR ANY POSSIBLE SPELLING OR GRAMMATICAL MISTAKES I COULD HAVE MADE IN THIS REPLY. ENGLISH NOT BEING MY FIRST LANGUAGE.

Spawning another java process after System.exit(0);

Hi everyone
I have an application that Im trying to test. Unfortunately one of these tests requires me to spawn another java process after a System.exit(0); has executed. Since this exits the VM its proving very difficult. Does anyone know of a way to restart the VM after the System.exit has run?
Thanks

Hi everyone
I have an application that Im trying to test.
Unfortunately one of these tests requires me to spawn
another java process after a System.exit(0); has
executed. Since this exits the VM its proving very
difficult. Does anyone know of a way to restart the VM
after the System.exit has run?Exactly what do you want to do?
If the application is supposed to only have one exit point then add a security manager and disallow all the other exit points. Then you can use Runtime.exec() to start the second application just before the real exit point.
However note that if there are other calls to System.exit in the application then it is very likely that this will cause some unexpected failures in terms of security exceptions.
You could also use Runtime.addShutdownHook() which would run your second app. The hook would be called as the application exits.
You might want to consider what happens if someone just kills the application (say with 'kill -9' or the windows task manager.) In either of those cases there is nothing that you can do in java to make that second application run.
You might also want to consider why you are doing this in the first place. As suggested a script solution is probably a better solution.

How to track System.exit(0) call

hi there,
how can i trace the System.exit(0) function call in my program.
i.e as we know which class is being loaded into the jvm by overriding
the classloader, can we similarly know when is our jvm going to be
destroyed. here iam invoking jvm from my windows program using invocation api.
any help is mostly appreciated.
thanks in advance
bye
ramana

Not sure I know what you are asking.
You could create a security manager which prevents exit() from being called.
You could replace System using the bootstrap command line option. Although if you do that you can not distribute it due to the license agreement. Once replaced you can do anything you want in the application.
You could use Runtime.addShutdownHook() if you just want to do something when the application exits.

Read sharing violation after System.exit in oracle lite DLL

I am using JRE 1.3 and successfully managed running some sql statements over jdbc.
When the java class is finished (implicit exit) then no error appears.
When I exit the code using System.exit(0) there is a windows dialog
showing a read access error AFTER the java class finished.
probably there is some cleanup the oracle DLL wants to do after the JVM exited?
Please help mailto:[email protected]
The sample code below can be used.
* Title:
* Description:
* Copyright: Copyright (c) 2001
* Company:
* @author Ivan Motsch
* @version 1.0
import java.util.*;
import java.io.*;
import java.sql.*;
public class TestOracleLite{
public TestOracleLite(){
 public void start(){
 Statement stm=null;
 Connection conn=null;
 try{
 Properties p=new Properties();
 p.setProperty("user","system");
 p.setProperty("password","manager");
 p.setProperty("DataDirectory","..\\..\\..\\TEMP\\ora4\\db");
 p.setProperty("Database","ORS");
 p.setProperty("IsolationLevel","Read Committed");
 p.setProperty("Autocommit","Off");
 p.setProperty("CursorType","Forward Only");
 String ps=getPropertiesAsString(p);
 Class.forName("oracle.lite.poljdbc.POLJDBCDriver");
 conn=DriverManager.getConnection("jdbc:polite:whatever"+ps);
 execSql(conn,
 "drop table test1 cascade"
 execSql(conn,
 "create table test1(pk number(32),ncol number(32),scol varchar2(2000),dcol date,rcol long raw)"
 conn.commit();
 execSql(conn,
 "insert into test1(pk,ncol,scol,dcol,rcol) values(?,?,?,?,?)",
 new Object[]{new Integer(1),new Integer(1111),"Test Text",new java.sql.Date(System.currentTimeMillis()),new byte[]{0,1,2,3,4,5,6,7,8,9,10}}
 conn.commit();
 readSql(conn,"select * from test1");
 catch(Exception e){
 e.printStackTrace();
 finally{
 if(conn!=null){
 try{
 conn.close();
 conn=null;
 catch(Exception e){e.printStackTrace();}
 private static String getPropertiesAsString(Properties p){
 StringBuffer buf=new StringBuffer();
 for(Iterator it=p.keySet().iterator();it.hasNext();){
 String key=(String)it.next();
 String val=p.getProperty(key);
 buf.append(";"+key+"="+val);
 return buf.toString();
 public boolean execSql(Connection conn,String s){
 return execSql(conn,s,(Collection)null);
 public boolean execSql(Connection conn,String s,Object[] binds){
 ArrayList list=new ArrayList();
 if(binds!=null) list.addAll(Arrays.asList(binds));
 return execSql(conn,s,list);
 public boolean execSql(Connection conn,String text,Collection binds){
 PreparedStatement stm=null;
 try{
 stm=conn.prepareStatement(text);
 if(binds!=null){
 int i=1;
 for(Iterator it=binds.iterator();it.hasNext();){
 Object o=it.next();
 if(o==null){
 stm.setNull(i,Types.VARCHAR);
 else if(o instanceof byte[]){
 stm.setBytes(i,(byte[])o);
 else{
 stm.setObject(i,o);
 i++;
 boolean b=stm.execute();
 System.out.println("status: "+(b?"ok":"failed"));
 return b;
 catch(SQLException e){
 System.out.println("status: "+"error"+" "+e);
 return false;
 finally{
 if(stm!=null) try{stm.close();}catch(Exception e){}
 public boolean readSql(Connection conn,String text){
 PreparedStatement stm=null;
 try{
 stm=conn.prepareStatement(text);
 ResultSet rs=stm.executeQuery();
 ResultSetMetaData meta=rs.getMetaData();
 System.out.print("col: ");
 for(int i=1,n=meta.getColumnCount();i<=n;i++){
 System.out.print(""+meta.getColumnName(i)+", ");
 System.out.println();
 while(rs.next()){
 System.out.print("row: ");
 for(int i=1,n=meta.getColumnCount();i<=n;i++){
 System.out.print(""+rs.getObject(i)+", ");
 System.out.println();
 return true;
 catch(SQLException e){
 System.out.println("status: "+"error"+" "+e);
 return false;
 finally{
 if(stm!=null) try{stm.close();}catch(Exception e){}
 static public void main(String[] args) {
 TestOracleLite t=new TestOracleLite();
 t.start();
 t=null;
 System.exit(0);

Hi
After system copy you need to do post system copy activities...
Please follow according to the installation Guide..
for example: your sld connection of your new system will be pointing to your source system. So you need to go to VA where in you can find SLD Data Supplier and change the host name, port no relavent to this i.e. your destination system...i.e.
new system.. In the same way you can follow doing the post installation activites will solve your issue.
Regards
Hari

Process in memory after System.exit(0)

I still see the process in memory after I exit the app. Do you think it is a JWS side effect?
Platform: W2K
Cheers,
Ivan

Ivan,
when you enable the 'java console' in Java Web Start->Preferences->Advanced->Show Java Console, you'll notice that you run into a java.security.accessControlException.
To avoid that, sign your jar file(s) and add the following to your jnlp file :
<security>
<all-permissions>
</security>
and it will work as expected!
Regards,
Patrick

Keep external process alive after System.exit(0)

I wish to start Outlook from my Java program and have my own program exit normally but keep alive the Outlook process. Besides, I am not interested in input/output/error streams.
public class OutlookStarter {
     public static void main(String[] args) throws Exception {
          new ProcessBuilder("cmd", "/c",
                    "\"C:\\Program Files\\Microsoft Office\\Office14\\outlook.exe\"")
                    .start();
}When I run this when Outlook is not started, my program will not exit until I close Outlook.
I really do not want to close Outlook just to exit my program (my real program has a Swing GUI and users must be able to close it).
Also when I run this when Outlook is already started, somehow my program DOES exit without closing the new Outlook window.
EDIT: I can add System.exit(0) and behavior is the same. I can use Runtime.getRuntime().exec and behavior is the same.
Edited by: Strider80 on Jan 12, 2011 7:27 AM

Strider80 wrote:
I wish to start Outlook from my Java program and have my own program exit normally but keep alive the Outlook process. Besides, I am not interested in input/output/error streams.
public class OutlookStarter {
     public static void main(String[] args) throws Exception {
          new ProcessBuilder("cmd", "/c",
                    "\"C:\\Program Files\\Microsoft Office\\Office14\\outlook.exe\"")
                    .start();
Did you try using [url http://www.computerhope.com/starthlp.htm]start ^[url http://www.computerhope.com/starthlp.htm]Microsoft DOS and command prompt^ ?
          new ProcessBuilder("cmd", "/c",
                    "start \"C:\\Program Files\\Microsoft Office\\Office14\\outlook.exe\"")
                    .start();

Disabling System.exit() and shutdown calls

I am trying to splice/hack together something that might stop a System.exit(0) call or perhaps some type of exit call for a Java application. The only thing I have come up with now is making an extension of SecurityException and putting the shutdown code within a try. Here is what I have so far...
class ExitTrappedException extends SecurityException {
     protected static void forbidSystemExitCall() {
          final SecurityManager securityManager = new SecurityManager() {
               public void checkPermission( java.security.Permission permission ) {
                    if( "exitVM".equals( permission.getName() ) ) {
                         throw new ExitTrappedException() ;
          System.setSecurityManager( securityManager ) ;
     protected static void enableSystemExitCall() {
          System.setSecurityManager( null ) ;
}And then utilizing it in the following manner...
forbidExitCall() ;
    try {
      // Call the "exiting" code here...
    } catch( ExitTrappedException e ) {
    } finally {
      enableExitCall() ;
    }I am not very comfortable setting the SecurityManager to null when re-enabling it to be honest. I am curious if someone might have a different solution to stopping a System.exit(0) call and the windows altf4+ shortcut. Any help would be much appreciated.

     static SecurityManager securityDefault = System.getSecurityManager();
     protected static void forbidSystemExitCall() {
          final SecurityManager securityManager = new SecurityManager() {
               public void checkPermission( java.security.Permission permission ) {
                    if( "exitVM".equals( permission.getName() ) ) {
                         throw new ExitTrappedException() ;
          System.setSecurityManager( securityManager ) ;
     protected static void enableSystemExitCall() {
          System.setSecurityManager( securityDefault ) ;
}how bout that?
Edited by: brillohead on Aug 4, 2008 11:21 AM

System Exit Overriding Busy Loop

Hi,
Why would the following code not result in a clean JVM termination when SIGINT is sent? The JVM appears to capture the SIGINT correctly (it hits the shutdown hook), but the System.exit(-1) call cannot seem to override the busy loop and terminate the spawned thread. Is this expected behavior for the VM?
public class TestSigInt {
     public TestSigInt()
          new Thread()
               public void run()
                    while(true)
          }.start();
          Runtime.getRuntime().addShutdownHook(new Thread()
               public void run()
                    System.exit(-1);
     public static void main(String[] args)
          TestSigInt tsi = new TestSigInt();
}Thanks,
hhung

Is this expected behavior for the VM?Yes. See javadoc for System.exit(), that leads to to Runtime.exit():
If this method is invoked after the virtual machine has begun its shutdown sequence then if shutdown hooks are being run this method will block indefinitely
So the method blocks (and presumably does nothing, but I admit I'm making up that last bit) if called as part of a shutdown hook.
the System.exit(-1) call cannot seem to override the busy loop and terminate the spawned threadRegardless of the fact that it's called from a shutdown hook, which previous messages (and the javadoc quoted) already question, there's nothing in the API javadoc that suggests that threads are gracefully "terminated".
This situation is not different from regular situations when you want to nicely end a thread in an otherwise running Java application: the API does not provide any built-in API (except Thread.stop() and destroy() which are deprecated and which use is strongly discouraged) to stop a running thread.
See Thread.interrupt() which somehow "kindly" requests interruption of a running thread, but this requires cooperation of the target thread (whose code shoud regularly poll Thread.getCurrentThread().isInterrupted() and terminate accrodingly).
The usual recommendation to make this more explicit in the code, is that the thread's code regularly checks a business-logic specific boolean, such as:
class StoppableTask implements Runnable {
    private boolean shouldContinue = true;
    public void run() {
        while (shouldContinue) {
            // do stuff
    public void requestStop() {
        shouldContinue = false;
public void class StopperThread {
    StoppableTask target;
    public void doOtherStuff() {
        target.requestStop();
}This requires cooperation form the target thread's code as well, so this is not conceptually different from the interrupt() scheme, it just has different scope (it won't unblock IOs for example).
Note that I deliberately used Runnable as opposed to Thread, first because it is a recommend practice (but you may know that already and your example was intentionally shorter to get to the point), second to highlight that the specific-solution does not use any built-in java.lang.Thread method.
Edited by: jduprez on Dec 8, 2009 11:28 AM

Catching System.Exit(value) in a unix script

I am migrating a java application from Windows to Unix, where on the Unix environment it will be run under a batch scheduler.
I am trying to figure out how to get Unix script 'visibility' to the contents of system.exit().
At program completion, system.exit is called with either a 0 (all's cool) or -1 (this dog won't hunt).
I cannot figure out how to get that value communicated back to the invoking script, which currently looks something like:
cp=<classpath>
rm -f /staging/*
$JAVA_HOME/bin/java ........
rc=$?
<if 'rc' = 0>
{ :perform this }
<if 'rc' = -1>
{ :perform this instead }
Any suggestions?

rc=$? suggests it's Bourne shell you're running the script with?
if [ $rc .eq. 0 ]; then
echo "Bingo!"
else
echo "Oh shit..."
fi
Better yet, do "man sh" from a unix command prompt -- it gives you the full scoop.

System Exit from JAVA Application

I need to call Oracle Reports from a JAVA application.
Does anyone have experience in this area?
One thing that comes to mind is to make a system exit and call the reports from the command line. Is this possible to be done? How?
Thank you for any help or suggestions.
Tina.

the best way to access the oracle database is via jdbc (see http://java.sun.com/products/jdbc/ ). if, however, you specifically need to run some oracle reporting s/w then you could run it as a separate process from your java application using Runtime.exec() (see http://java.sun.com/j2se/1.3/docs/api/java/lang/Runtime.html#exec(java.lang.String) ) which returns a Process object. you can then read its output with the Process object's getInputStream() method (this gives you an InputStream which is the data piped from the standard output stream of the process).
hth,
jonesy (sun developer technical support)

System.exit(0) problem

Hi there,
I open C++ GUI application from Java (using JNI native call). When user clicks "x" and closes GUI application, I'd like to shutdown JVM also. In my code, when user clicks "x", C++ side calls Java method (that contains System.exit(0) call) and this results in the java.exe - Application Error: "The instruction at 0x0 referenced at 0x0. The memory couldn't be read".
I use Jace to handle JNI calls but this sounds like a pure JNI problem.
Many thanks in advance.
Kalle.

System.exit(0)kills the main thread but you still is in the native function. Return has no a valid address. CallSystem.exit(0) only from JAVA code.

The ABAP call stack was: SYSTEM-EXIT of program BBPGLOBAL

Hi
We are using SRM 5.0. We are facing a strange problem. We are able to see the initial screen of SRM EBP in the browser. But once the user name and password are provided the system goes for a dump with the following error:
The following error text was processed in the system SS0 : System error
The error occurred on the application server <Server Name> and in the work process 0 .
The termination type was: ABORT_MESSAGE_STATE
The ABAP call stack was: SYSTEM-EXIT of program BBPGLOBAL
SM21 Log:
Short Text
 Transaction Canceled &9&9&5 ( &a &b &c &d &e &f &g &h &i )
 The transaction has been terminated. This may be caused by a
 termination message from the application (MESSAGE Axxx) or by an error
 detected by the SAP System due to which it makes no sense to proceed
 with the transaction. The actual reason for the termination is
 indicated by the T100 message and the parameters.
Transaction Canceled ITS_P 001 ( )
Message Id: ITS_P
Message No: 001
I just checked these threads but did not help much,
RABAX_STATE error after loggin into BBPSTART service in SRM 4.
ITS_TEMPLATE_NOT_FOUND error
Besides I tried this note: 790727 as well, still I get the same error.
Any help would be highly appreciated.
Thanks in advance
Kathirvel Balakrishnan

Hi
Please do the following steps.
When you are using the Internal ITS,you need not run the report W3_PUBLISH_SERVICES.(only SIAC_PUBLISH_ALL_INT )
ALso pls check the foll:
-->activate the services through SICF tcode.
> Go to SICF transaction and activate the whole tree under the node Default host>sap>bc>gui>sap>its.
>Also maintain the settings in SE80>utilities>settings>internet transaction server-->test service/Publish. (BBPSTART , BBPGLOBAL etc)
Table TWPURLSVR should have entries for the / SRM server line as well as gui and web server.
Could you please review again the following steps ?
Did you check that ICM was working correctly (Transaction - SMICM) ?
1-Activate the necessary ICF services
With transaction SICF and locate the
services by path
/sap/public/bc/its/mimes
/sap/bc/gui/sap/its/webgui
2- Publish the IAC Services
With Transaction SE80 locate from
the menu Utilities -> Settings ->
Internet Transaction Server (Tab) ->
Publish (Tab) and set On Selected
Site = INTERNAL.
3- Locate the Internet Services SYSTEM and WEBGUI.
Publish these services with the Context
Menu -> Publish -> Complete Service
4- Browse to http://<server>:<icmport>/sap/bc/gui/
sap/its/webgui/! and login to the
webgui.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Calling System.exit(0) from an applet

Hello,
I have a weird problem.
First... my applet has full permissions in the java.policy file.
problem:
When I call System.exit(0) from the applet (jbutton's action listener), the applet disappears from the browser window and the browser freezes.
but
if I display a messagedialog (JoptionPane) before calling System.exit(0) ... everything works fine (after I press ok on the message dialog, the browser window disappears)
here's my code
<CODE>
public class testApp extends JApplet{
public void init(){
System.err.println("hello");
JButton button = new JButton("Exit");
button.addActionListener(new ActionListener(){
public void actionPerformed(ActionEvent e){
JOptionPane.showMessageDialog(new JFrame(),"Exiting...");
System.exit(0);
this.getContentPane().add(button);
</CODE>
what am I missing?

an applet has security restrictions that forbids it from accessing a client file system. BUT there are ways like signing your applet or just asking the user to change the security setting when he calls the applet.
This link shows the steps involved in signing an applet very clearly. :-http://developer.java.sun.com/developer/technicalArticles/Security/Signed/
Or the user(client) can go to the "Internet Option" under the Tools of the web browser(IE). Go to security and change to custom security for the Internet.(Caution the user needs to return the security to default after finishing accessing the applet). Click to "Custom Java Setting" button. If you don't see a "Custom Java Setting" button below then scroll down to "Java Permissions" option and select custom. Now you will see the "Custom Java Setting" button. Go there and select "edit permission" tab. Under "Unsigned Content" select enable. This will grant full permission.

Is System.exit() a good call to use?

I have a program that checks for updates in the db. If there are no updates in the database I want the program to stop. There are also many other conditions that would cause the program to stop. None of them are "Errors" so I wasn't using Exceptions to end the program The program runs from a command line or from chron job. Is it safe / OK to use System.exit() to do this?

As you describe it, I'd say yes. System.exit() is the way to end your program.
The danger of System.exit() is if a class you write will be reused in some other system. In that case, System.exit() could be entirely inappropriate in that context, thus preventing your class from being reusable.
If you only call System.exit() in your main() method, you'll probably be OK.

NoClassDefFoundError after System.exit() is called.

Similar Messages

Maybe you are looking for