Error in XMLDiff Bean, System.exit() is being called in setFiles() ?

When I call the setFiles() method in XMLDiff and the files contain dtd references, my application will shut down competely as though System.exit() is being called from within the XMLDiff bean. I have tested this with the XMLDiff demo and it also shut down when a dtd reference was in the files.

The version of XDK is 9.2.0.2.0
The test case is the "family.xml" in the demo\java\parser\common directory using the XMLDiffSample application. What I did was to try to compare the family.xml against itself. When I do that it shuts down the demo application as though System.exit() has been called.
Setting the standalone="yes" did in fact cause it to work properly, but I am not sure why?

Similar Messages

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.

User exit not being called

Hi,
We have implemented user exit EXIT_SAPLMRMH_015, include ZXM08U26.
Problem 1:
When we tested in development system by processing a Idoc in debug, mode this user exit got called and the code in the user exit (include ZXM08U26) was executed.
Now we moved our changes to the quality system. Again we tested in quality by processing a idoc in debug mode. The user exit is getting called, but the code is not getting executed ( its not going inside include ZXM08U26). Why?
Problem 2:
In quality when I try to put break points in include ZXM08U26, a message pops up saying "The position of a breakpoint could not be ascertained". Why cant I put breakpoints?
The project (in CMOD) and the include (ZXM08U26) are all active in quality.
Thanks in advance.
Mick

When you create/change a project, you must create a correction. This correction contains only the attributes and the SAP enhancements associated with a project, as well as a program that is automatically started with the transport and activates the project in the target system. Since activating a project affects all components, you should transport all components associated with a project at the same time, in other words with the same transport request. To ensure that the project is activated automatically in the target system, the correction that contains the program concerned must also be in the same transport request. If this is not the case, or the project has not been activated in the target system for other reaons, you can also activate it by manually starting the program (RSMODACT).

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

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.

To trap System.exit(0)

Hi All,
In one of our code we are saying System.exit(0),System.exit(1),System.exit(-1) based on certain condition that occur in the program. Could any one let us know how to trap the integer returned to the OS when System.exit(x) is called.
Regards,
Vinodramu

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.

System.exit(o) in Swing

Hi,
In my Swing application, as soon as I start the main() method, a dialog containing Username and Password fields with OK and Cancel buttons gets popped-up. I have a propertyChangeListener which gets notified when Ok or cancel is pressed and when Cancel is pressed, System.exit(0) is called to exit the JVM.
So, there are two threads running -
One - the main thread which invokes the dialog pop-up
Second - the propertychangelistener which calls the System.exit(0) on pressing Cancel button.
So, at times, after pressing cancel button, the application does not exit but invokes the previously running thread (main thread). But this does not happen always.
Could you please let me know why the application does not terminate completely and how to resolve this?
Thanks in advance!

Hi,
As I had already mentioned in my previous post -
Here is the pseudo-code which fails to terminate on pressing Cancel button at times.
================The Login dialog code=============
public LoginDialog()
// Other code
JOptionPane optionPane = new JOptionPane(array, JOptionPane.QUESTION_MESSAGE, JOptionPane.YES_NO_OPTION, null, options, options[0]);
optionPane.addPropertyChangeListener(new PropertyChangeListener()
public void propertyChange(PropertyChangeEvent e)
          Object value = optionPane.getValue();
          if (value.equals(YES))
          else
// user closed dialog or clicked cancel
setVisible(false);
System.exit(0);
===============The main thread===================
This main() method calls the logindialog with username and passwrd as parameters.
So, initially, the main() thread is started and the login dialog is displayed. On pressing Cancel in this dialog, the control goes to propertyChangeListener of the loginDialog() and calls System.exit(0) which should terminate the entire application, but at times, the previously running main thread is resumed and the application is not terminated.
Please clarify why this happens.
Thanks in advance!!
});

Kill and System.exit

Is there a way (with Linux) to issue the kill command on your java process so that System.exit(0) is called and you know that your shutDownHooks will run?

Thanx again for the reply, Freddy
first things first:
System.exit(0) does not work in this case..
and the code is reached..
// main class
public class AdminApp {
public AdminApp() {
public static void main(String[] args) {
AdminApp adminApp1 = new AdminApp();
AdminFrame frame = new AdminFrame();
/// admin frame class
public class AdminFrame extends JFrame{
public AdminFrame() {
addWindowListener(new WindowAdapter() {
public void windowClosing(WindowEvent e) {
System.exit(0);
this.pack();
this.setSize(600,480);
this.setVisible(true);
groupsMenuItem.addActionListener(new ActionListener() {
public void actionPerformed(ActionEvent ae) {
desktop.add(new AdminGroups());
//admingroups class
public class AdminGroups extends JInternalFrame {
private JTextArea textArea = new JTextArea();
private JScrollPane scrollPane = new JScrollPane();
JPanel groupPanel = new JPanel();
XYLayout xYLayout1 = new XYLayout();
public AdminGroups() {
setSize(200,300);
setTitle("Edit Text");
setMaximizable(true);
setIconifiable(true);
setClosable(true);
setResizable(true);
scrollPane.getViewport().add(textArea);
getContentPane().setLayout(new BorderLayout());
getContentPane().add(scrollPane,BorderLayout.CENTER);
try {
jbInit();
catch(Exception e) {
e.printStackTrace();
getContentPane().add(groupPanel);
private void jbInit() throws Exception {
groupPanel.setLayout(xYLayout1);
}

How do I exit a java program based on condition can i use system.exit

I have java program that is called by another program that I dont have control on. My program returns a bigdecimal... but if the ordernumber is empty in my program i dont wnat to do anything.. does system.exit work in that condition... i put it int he else if ordernumber is empty condition.. but i dont think that is the right approach..

When software module is expected to bring some result, it should bring the result, positive or negative. I think you should check what your counterpart software expects as positive or negative result. And then implement your software this way. You can use System.exit, but this call is employed usually to indicate status with the software after it's completion and not to return any resulting value.
http://java.sun.com/j2se/1.4.2/docs/api/java/lang/System.html#exit(int)

System.exit(0)   error in program.

Any help appreciated. Let me first put my code here:
Converts money using CurrencyConverter, there's another class I haven't posted here!! (which calculates conversion)
import java.util.* ;
public class CurrencyConverterTester
public static void main(String[] args)
    Scanner in = new Scanner(System.in) ;
    System.out.println("How many euros is one dollar?") ;
    String input = in.nextLine() ;
    double rate = Double.parseDouble(input) ;
    CurrencyConverter myconverter = new CurrencyConverter(rate);
    System.out.println("Dollar value (Q to quit)") ;
    input = in.nextLine() ;
    while (true) {
      if (input == "Q"){
        System.exit(0);
        break;}
      else {
      System.out.println(input + " dollar = " + myconverter.convert(Double.parseDouble(input)) + " euros");
      input = in.nextLine();
      continue;}
}The issue is that the program won't terminate when I enter Q as my input?? I'm guessing it might have something to do my conversion from string to double in the 'else' statement, but not sure. Also, if you can suggest a more simpler method for the last 'while' statement, that would be helpful as well. Thanks. (noob to java)

paulcw wrote:
Curse Gosling for making + syntactic sugar for string append, but not overloading any other operators.@Paul
What did you expect from a duck ;-)
Seriously, yep, maybe it would have been better for noobs if the syntax of Java Strings was consistent with other kinds of Object... or maybe it would have been better if == was compiler-magiced into stringA.equals(stringB)... and the left and right shift operators have promise, and of course that way lies MADNESS, as witnessed in C++ ;-)
@OP... You are (IMHO) using the break, continue and especially System.exit() inappropriately... see my comments in your code...
    System.out.println("Dollar value (Q to quit)") ;
    input = in.nextLine() ;
    // while-true-loops are a "fairly usual" way of doing this kind of stuff,
    // but that doesn't make them "the preferred option". Typically you would
    // explore more "vanilla approaches" (which don't rely on the break and
    // continue statements)... leaping straight to the "tricky approach" means
    // you haven't (most often out of sheer laziness) thought it through... and
    // ALL good computer programs are thoroughly thought through (yep, try
    // saying that three times fast, especially after three beers).
    while (true) {
      // You don't compare Strings using ==
      if ( "Q".equalsIgnoreCase(input) ) {
        // Either of the following statements will do the job. The call to exit
        // will exit the JVM, therfore the break statement cannot be reached,
        // so it is superflous, so it's presence is just a bit confusing. Having
        // said that, "real programmers" don't use System.exe routinely, only in
        // the case of an emergency, such as handling a fatal-error, such as an
        // out-of-memory condition... an even then it's usually indicative of a
        // poor "system design", because it terminates the JVM which is running
        // this program without giving anything else in the program a chance to
        // clean-up after itself... like ask the user if they want to save there
        // work, or whatever.
        // I would use break (if anything) instead of System.exit
        // ... and if I wrote the Java tutorials, exit wouldn't be mentioned at
        // all until both "normal" flow control, and exception handling had both
        // been thoroughly covered.
        System.exit(0);
        break;
      } else {
        // I would break this line up, probably into three lines, simply becuase
        // it's syntatically "a long line".
        // Also the name "myconverter" doesn't tell what the class is/does.
        // IMHO, currencyConverter would be a better (more meaningful) name.
        // HERE'S HOW I WOULD WRITE IT
        // double dollars = Double.parseDouble(input);
        // double euros = currencyConverter.convert(dollars);
        // System.out.println(input + " dollar = " + euros + " euros");
        System.out.println(input + " dollar = " + myconverter.convert(Double.parseDouble(input)) + " euros");
        input = in.nextLine();
        // This continue statement is superflous. continue says "go back to the
        // top of loop, reevaluate the loop-condition (true in this case) and
        // (if the condition is still true) "Play it again Sam".
        // ... which is exactly what will happen without this continue statement
        // and hence (IMHO) your code is easier to follow without it, simply
        // because another programmer may waste there time trying to figure out
        // WHY that continue statement is present.
        continue;
    }*ALSO:* The format of that code totally sucks. Braces all over the place; improper indentation. No wonder you're struggling to read your own code. Please read and abide the [The Java Code Conventions|http://java.sun.com/docs/codeconv/] (at least until you have the requisite experience to formulate credible and compelling arguments as to why your "style" is superior to the standard, and that's no small ask). Yes this is *important*... trust me on this (for now)... especially if you are going to ask for help on the forums... You're effectively wasting our time asking us to decipher your code because you are too lasy to format it correctly... and I for one find that "self entitled" attitude ugly, and offensive... Help us help you... you know?
And BTW.... Here's how I would actually do it.... no funky while-true, break, or continue... just a plain-ole'-while-woop....
package forums;
import java.util.Scanner;
public class KRC
private static final Scanner SCANNER = new Scanner(System.in);
public static void main(String[] args) {
    try {
      String input = null;
      while ( !"Q".equalsIgnoreCase(input=enterDollarAmount()) ) {
        System.out.println(input + " dollars is " + Double.parseDouble(input) + " euros.");
        System.out.println();
    } catch (Exception e) {
      e.printStackTrace();
private static String enterDollarAmount() {
    System.out.print("Please enter an amount in dollars : ");
    return SCANNER.nextLine();
}Edited by: corlettk on 25/10/2009 10:21 ~~ Distant Monarching Forum Markup!

Mac Error on System.exit(1);

When I close my application, which is exported as runnable jar, using System.exit(1); I get an error.
Mine is in Dutch, but translated it is:
The Java-JAR-file 'file.jar' can't be started.
Check Console for any error messages.
Does anyone recognize this error?

A non-zero return value usually indicates an error.
Maybe Mac OS X takes this to the logical conclusion and shows the error when your app returns a non-zero return value.
Try gimbal2s suggestion and tell us if it changes anything.

Error on System.exit(0)

Hi everybody.
I'm running an application with JFrames. And everything works fine. But when i'm trying to close the main JFrame and reach the method System.exit(0); i get the next windows error.
instruction on "0x77a7bb99" references to memory on "0x1c553ce0". Memory can't read.
Do you know why i get this kind of error.
I'm using java 1.4.1_01.
Thank u for your time :)

If i upgrade to 1.5 i don't see de Error dialog. But i get an EXCEPTION_ACCESS_VIOLATION:
# An unexpected error has been detected by HotSpot Virtual Machine:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x77a7bb99, pid=2184, tid=2848
# Java VM: Java HotSpot(TM) Client VM (1.5.0_02-b09 mixed mode, sharing)
# Problematic frame:
# C [ole32.dll+0x2bb99]
--------------- T H R E A D ---------------
Current thread (0x00ac70a8): VMThread [id=2848]
siginfo: ExceptionCode=0xc0000005, reading address 0x0c6c3d80
Registers:
EAX=0x0c6c3d80, EBX=0x0be13714, ECX=0x0be137b8, EDX=0x80000001
ESP=0x02cafc28, EBP=0x02cafc6c, ESI=0x00000000, EDI=0x0be01568
EIP=0x77a7bb99, EFLAGS=0x00010246
Top of Stack: (sp=0x02cafc28)
0x02cafc28: 0c6c3d80 00000001 0be13714 00000000
0x02cafc38: 00000000 0be079e8 0009c320 00000001
0x02cafc48: 0be00ec0 00000000 0009c320 0be05680
0x02cafc58: 00000001 00000001 0009c320 00000001
0x02cafc68: 0000000a 02cafc94 77ab2524 0be13714
0x02cafc78: 0be13710 0be13794 00000000 00000000
0x02cafc88: 00000000 00000001 0be14010 02cafcb4
0x02cafc98: 77ab0550 00000002 0be137b8 0be13710
Instructions: (pc=0x77a7bb99)
0x77a7bb89: 47 14 50 8b 08 ff 51 08 83 67 14 00 8b 47 18 50
0x77a7bb99: 8b 08 ff 51 10 f6 47 04 08 75 14 8b 4b 68 85 c9
Stack: [0x02c70000,0x02cb0000), sp=0x02cafc28, free space=255k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [ole32.dll+0x2bb99]
C [ole32.dll+0x62524]
C [ole32.dll+0x60550]
C [ole32.dll+0x604ad]
C [dpDevClt.dll+0x3044]
C [ntdll.dll+0x30e7]
C [ntdll.dll+0xee02]
C [KERNEL32.DLL+0x269c3]
C [MSVCRT.dll+0x7cd8]
V [jvm.dll+0x117825]
V [jvm.dll+0x1179c5]
V [jvm.dll+0x11775a]
C [MSVCRT.dll+0x85bc]
C [KERNEL32.DLL+0xb388]
VM_Operation (0x0cbaf70c): exit, mode: safepoint, requested by thread 0x030a7e30
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x030c0468 JavaThread "RMI ConnectionExpiration-[IP:1099]" daemon [_thread_blocked, id=2716]
0x030742b0 JavaThread "TimerQueue" daemon [_thread_blocked, id=2820]
0x00286d68 JavaThread "DestroyJavaVM" [_thread_blocked, id=2764]
0x030a7e30 JavaThread "AWT-EventQueue-0" [_thread_blocked, id=1772]
0x0306c008 JavaThread "AWT-Shutdown" [_thread_blocked, id=2108]
0x02e4df58 JavaThread "Thread-2" [_thread_in_native, id=2468]
0x03021b70 JavaThread "Java2D Disposer" daemon [_thread_blocked, id=2412]
0x00acdd60 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=2636]
0x00acc910 JavaThread "CompilerThread0" daemon [_thread_blocked, id=2704]
0x00ac8d90 JavaThread "Finalizer" daemon [_thread_blocked, id=2856]
0x00a99dc0 JavaThread "Reference Handler" daemon [_thread_blocked, id=2772]
Other Threads:
=>0x00ac70a8 VMThread [id=2848]
VM state:at safepoint (shutting down)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x00286300/0x00000b18] Threads_lock - owner thread: 0x00ac70a8
Heap
def new generation total 576K, used 359K [0x22af0000, 0x22b90000, 0x22fd0000)
eden space 512K, 57% used [0x22af0000, 0x22b39c08, 0x22b70000)
from space 64K, 100% used [0x22b70000, 0x22b80000, 0x22b80000)
to space 64K, 0% used [0x22b80000, 0x22b80000, 0x22b90000)
tenured generation total 1408K, used 955K [0x22fd0000, 0x23130000, 0x26af0000)
the space 1408K, 67% used [0x22fd0000, 0x230beea8, 0x230bf000, 0x23130000)
compacting perm gen total 8192K, used 3377K [0x26af0000, 0x272f0000, 0x2aaf0000)
the space 8192K, 41% used [0x26af0000, 0x26e3c510, 0x26e3c600, 0x272f0000)
ro space 8192K, 66% used [0x2aaf0000, 0x2b0488a8, 0x2b048a00, 0x2b2f0000)
rw space 12288K, 46% used [0x2b2f0000, 0x2b884818, 0x2b884a00, 0x2bef0000)
Dynamic libraries:
0x00400000 - 0x0040c000      C:\Archivos de programa\Java\jdk1.5.0_02\bin\java.exe
0x78460000 - 0x784e3000      C:\WINNT\system32\ntdll.dll
0x78ff0000 - 0x79052000      C:\WINNT\system32\ADVAPI32.dll
0x79450000 - 0x7950d000      C:\WINNT\system32\KERNEL32.DLL
0x77120000 - 0x77191000      C:\WINNT\system32\RPCRT4.DLL
0x78000000 - 0x78045000      C:\WINNT\system32\MSVCRT.dll
0x6d6b0000 - 0x6d835000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\client\jvm.dll
0x77e10000 - 0x77e6f000      C:\WINNT\system32\USER32.dll
0x77f40000 - 0x77f7b000      C:\WINNT\system32\GDI32.dll
0x77550000 - 0x77581000      C:\WINNT\system32\WINMM.dll
0x6d2f0000 - 0x6d2f8000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\hpi.dll
0x68f70000 - 0x68f7b000      C:\WINNT\system32\PSAPI.DLL
0x6d680000 - 0x6d68c000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\verify.dll
0x6d370000 - 0x6d38d000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\java.dll
0x6d6a0000 - 0x6d6af000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\zip.dll
0x6d070000 - 0x6d1d6000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\awt.dll
0x77800000 - 0x7781e000      C:\WINNT\system32\WINSPOOL.DRV
0x79520000 - 0x79530000      C:\WINNT\system32\MPR.DLL
0x75e30000 - 0x75e4a000      C:\WINNT\system32\IMM32.dll
0x77a50000 - 0x77b3f000      C:\WINNT\system32\ole32.dll
0x727a0000 - 0x727e6000      C:\WINNT\system32\ddraw.dll
0x72840000 - 0x72846000      C:\WINNT\system32\DCIMAN32.dll
0x72c90000 - 0x72d24000      C:\WINNT\system32\D3DIM700.DLL
0x77590000 - 0x777db000      C:\WINNT\system32\shell32.dll
0x70bd0000 - 0x70c35000      C:\WINNT\system32\SHLWAPI.dll
0x71710000 - 0x71794000      C:\WINNT\system32\COMCTL32.dll
0x6d2b0000 - 0x6d2ed000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\fontmanager.dll
0x6d530000 - 0x6d543000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\net.dll
0x74fe0000 - 0x74ff4000      C:\WINNT\system32\WS2_32.dll
0x74fd0000 - 0x74fd8000      C:\WINNT\system32\WS2HELP.DLL
0x6d550000 - 0x6d559000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\nio.dll
0x10000000 - 0x10011000      C:\mobileclient\bin\oljdbc40.dll
0x03540000 - 0x035cc000      C:\mobileclient\bin\olobj40.dll
0x035d0000 - 0x035de000      C:\mobileclient\bin\olaes.dll
0x035e0000 - 0x0360c000      C:\mobileclient\bin\olStdDll.dll
0x75000000 - 0x75009000      C:\WINNT\system32\WSOCK32.dll
0x70200000 - 0x70296000      C:\WINNT\system32\WININET.dll
0x79640000 - 0x796c7000      C:\WINNT\system32\CRYPT32.dll
0x77410000 - 0x77420000      C:\WINNT\system32\MSASN1.DLL
0x779b0000 - 0x77a4b000      C:\WINNT\system32\OLEAUT32.dll
0x780c0000 - 0x78121000      C:\WINNT\system32\MSVCP60.dll
0x0ba30000 - 0x0ba3b000      C:\mobileclient\bin\olil125x.dll
0x0ba40000 - 0x0ba68000      C:\mobileclient\bin\olod2040.dll
0x0ba70000 - 0x0baeb000      C:\mobileclient\bin\olsql40.dll
0x0bb30000 - 0x0bb48000      C:\WINNT\system32\VFJavaW42.dll
0x0bb50000 - 0x0bbc0000      C:\WINNT\system32\VFinger.dll
0x75120000 - 0x7516f000      C:\WINNT\system32\NETAPI32.dll
0x790d0000 - 0x790df000      C:\WINNT\system32\Secur32.dll
0x77bf0000 - 0x77c01000      C:\WINNT\system32\NTDSAPI.dll
0x77980000 - 0x779a4000      C:\WINNT\system32\DNSAPI.DLL
0x77950000 - 0x7797b000      C:\WINNT\system32\WLDAP32.DLL
0x75170000 - 0x75176000      C:\WINNT\system32\NETRAP.dll
0x75100000 - 0x7510f000      C:\WINNT\system32\SAMLIB.dll
0x65440000 - 0x65447000      C:\WINNT\system32\wtsapi32.dll
0x664d0000 - 0x664da000      C:\WINNT\system32\UTILDLL.dll
0x77510000 - 0x77532000      C:\WINNT\system32\TAPI32.dll
0x783c0000 - 0x78451000      C:\WINNT\system32\SETUPAPI.dll
0x78df0000 - 0x78e52000      C:\WINNT\system32\USERENV.DLL
0x655e0000 - 0x655ed000      C:\WINNT\system32\WINSTA.dll
0x68950000 - 0x6895b000      C:\WINNT\system32\REGAPI.dll
0x77300000 - 0x77317000      C:\WINNT\system32\MPRAPI.dll
0x77390000 - 0x773bf000      C:\WINNT\system32\ACTIVEDS.DLL
0x77360000 - 0x77383000      C:\WINNT\system32\ADSLDPC.DLL
0x77830000 - 0x7783e000      C:\WINNT\system32\RTUTILS.DLL
0x0bc70000 - 0x0bc84000      C:\WINNT\system32\SMJavaW.dll
0x0bc90000 - 0x0bca3000      C:\WINNT\system32\ssl.DLL
0x0bcd0000 - 0x0bce7000      C:\WINNT\system32\sslBiometrika.dll
0x0bd00000 - 0x0bd1e000      C:\WINNT\system32\fx3scan.dll
0x0bd30000 - 0x0bd91000      C:\WINNT\system32\fx3.dll
0x77820000 - 0x77827000      C:\WINNT\system32\VERSION.dll
0x75980000 - 0x75986000      C:\WINNT\system32\LZ32.DLL
0x0beb0000 - 0x0bec9000      C:\WINNT\system32\sslFile.dll
0x76b10000 - 0x76b4e000      C:\WINNT\system32\comdlg32.dll
0x0bee0000 - 0x0bef7000      C:\WINNT\system32\sslST.dll
0x0bf10000 - 0x0bf5d000      C:\WINNT\system32\tci.dll
0x0bf70000 - 0x0bf89000      C:\WINNT\system32\sslUareU.dll
0x0bfa0000 - 0x0bfba000      C:\WINNT\system32\dpFpFns.dll
0x0bfc0000 - 0x0bfca000      C:\WINNT\system32\dpDevDat.dll
0x0bfd0000 - 0x0bff3000      C:\WINNT\system32\dpDevClt.dll
0x0c000000 - 0x0c071000      C:\WINNT\system32\dpFtrEx.dll
0x0c080000 - 0x0c0db000      C:\WINNT\system32\dpMatch.dll
0x0c560000 - 0x0c5f0000      C:\WINNT\system32\CLBCATQ.DLL
0x0c680000 - 0x0c6be000      C:\Archivos de programa\DigitalPersona\Bin\DPPS.dll
0x7ca00000 - 0x7ca23000      C:\WINNT\system32\rsabase.dll
0x0c6d0000 - 0x0c6f3000      C:\WINNT\system32\rsaenh.dll
0x0c700000 - 0x0c904000      C:\WINNT\system32\msi.dll
0x74f80000 - 0x74f9e000      C:\WINNT\system32\msafd.dll
0x74fc0000 - 0x74fc7000      C:\WINNT\System32\wshtcpip.dll
0x77840000 - 0x7784c000      C:\WINNT\System32\rnr20.dll
0x77320000 - 0x77333000      C:\WINNT\system32\iphlpapi.dll
0x77500000 - 0x77505000      C:\WINNT\system32\ICMP.DLL
0x774c0000 - 0x774f3000      C:\WINNT\system32\RASAPI32.DLL
0x774a0000 - 0x774b1000      C:\WINNT\system32\RASMAN.DLL
0x77340000 - 0x77359000      C:\WINNT\system32\DHCPCSVC.DLL
0x777e0000 - 0x777e8000      C:\WINNT\System32\winrnr.dll
0x777f0000 - 0x777f5000      C:\WINNT\system32\rasadhlp.dll
0x6d660000 - 0x6d666000      C:\Archivos de programa\Java\jdk1.5.0_02\jre\bin\rmi.dll
VM Arguments:
java_command:
Environment Variables:
CLASSPATH=C:\mobileclient\bin\msync.jar;C:\codigos\almacen\classes;C:\mobileclient\bin\olite40.jar;C:\mobileclient\bin\webtogo.jar
PATH=c:\j2sdk1.4.1_01\bin\;;C:\mobileclient\bin;C:\oracle\ora92\bin;C:\Archivos de programa\Oracle\jre\1.3.1\bin;C:\Archivos de programa\Oracle\jre\1.1.8\bin;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Archivos de programa\Symantec\pcAnywhere\;c:\winnt;c:\winnt\respair;c:\grupotelnet\classes;c:\grupotelnet;c:\GrupoTelnet\comandera;c:\GrupoTelnet\comandera\config;c:\j2sdk1.4._01\bin;C:\WINNT\system32;c:\grupotelnet\classes;c:\GrupoTelnet;C:\mobileclient\bin
USERNAME=Administrador
OS=Windows_NT
PROCESSOR_IDENTIFIER=x86 Family 15 Model 1 Stepping 3, GenuineIntel
--------------- S Y S T E M ---------------
OS: Windows 2000 Build 2195 Service Pack 4
CPU:total 1 family 15, cmov, cx8, fxsr, mmx, sse, sse2, ht
Memory: 4k page, physical 515568k(63456k free), swap 876852k(302676k free)
vm_info: Java HotSpot(TM) Client VM (1.5.0_02-b09) for windows-x86, built on Mar 4 2005 01:53:53 by "java_re" with MS VC++ 6.0

Error while invoking bean "delivery": Waiting for response has timed out.

Hello,
I am running a process that currently catches an exception from a partnerlink. When the exception is caught I send an email and the process exits. When I submit a request from the BPEL console, I have to wait until the JTA timeout before the page returns. However, the instance completes successfully and I receive the email before the timeout happens. This is what I see in the logs. When I look at the audit and activity flow, all of the activities were timestamped prior to the exception being thrown. Has anyone seen this behavior or know what is going on. Is there a problem sending email in a catch or catchAll block?
<2009-04-19 22:33:41,859> <ERROR> <iCareTest.collaxa.cube> <BaseCubeSessionBean::logError> Error while invoking bean "delivery": Waiting for response has timed out. The conversation id is cf9324c9be114336:513ede58:120c17e1922:-7fc0. Please check the process instance for detail.
com.oracle.bpel.client.delivery.ReceiveTimeOutException: Waiting for response has timed out. The conversation id is cf9324c9be114336:513ede58:120c17e1922:-7fc0. Please check the process instance for detail.
Thanks in advance
Jim

There is no issue the reason why it times out is because you don't have a reply back to the client in your catch all.
If you look at your process you will see that the defaul reply is in the main scope. When the catch all is invoked this reply is by passed, therefore no reply is sent.
PLease a reply in your catch all back to the client and it will work.
cheers
James

Problem while determining receivers using interface mapping: "SYSTEM FAILURE" during JCo call. Bean SMPP_CALL_JAVA_RUNTIME3 not found

We have a SOAP to PROXY scenario Which is in Production.
We keep getting the Error:
" Problem while determining receivers using interface mapping: "SYSTEM FAILURE" during JCo call. Bean SMPP_CALL_JAVA_RUNTIME3 not found on host XXXXXX, ProgId =AI_RUNTIME_XXX.
We are using Standard Receiver Determination with single receiver without any condition. And no mapping being used in interface determination.
What are all the possible situation where we face such as this issue in Production.

Please check the SAP note
# 1706936 - messages fails with error java.lang.RuntimeException Bean SMPP_CALL_JAVA_RUNTIME3 not found
1944248 - PI unstable due to JCO_SYSTEM_FAILURE mapping issues

Call to java bean but code not being executed.

Making a call to my javabean class called ch06_03.java from a jsp program shown below:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>Using a java package.</title>
</head>
<body>
<% beans.ch06_03 messager = new beans.ch06_03(); %>
The message is: <%= messager.msg() %>
</body>
</html>
The call from jsp to javabean program is only returning the hello from java and NOT EXECUTING ANY OF THE CODE in the msg() method. I am checking my table landings_hold and nothing is there, my log file shows nothing. Why is the code not being executed except for the return statement?
My javabean program is shown below:
package beans;
import java.io.*;
import java.util.*;
import java.text.*;
import java.sql.*;
public class ch06_03 {
StringTokenizer st1;
          String val1, val3, val4, val5, val9, val10, val11, val12, val13, val14, val16;
          String val2, val6, val7, val8, val15, val17, val18, val19, val20;
          int cnt;
          String filetext = "Starting RIFIS Upload";
          java.util.Date d = new java.util.Date();
          SimpleDateFormat form = new SimpleDateFormat("dd/MMM/yyyy hh:mm:ss");
          String dateString = form.format(d);
public String msg() throws Exception {
     try {
     Class.forName("oracle.jdbc.driver.OracleDriver").newInstance();
Connection conn = DriverManager.getConnection("jdbc:oracle:thin:@xxxxx.xxxx.xxx:1521:xx","xxxxxx","xxxx");
          Statement st = conn.createStatement();
     File f = new File("C://upload");
          FileWriter outFile = new FileWriter("C://RIFIS/log/logfile.txt", true);
          outFile.write(System.getProperty("line.separator"));
          outFile.write(filetext+" - "+dateString);
          if (f.isDirectory())
          { String [] s = f.list();
          for (int i=0; i<s.length; i++)
          { outFile.write(System.getProperty("line.separator"));
               outFile.write("Found file - "+f+"/"+s);
          FileReader file = new FileReader(f+"/"+s[i]);
               File inputFile = new File(f+"/"+s[i]);
                    File outputFile = new File("C://RIFIS/archive/"+s[i]);
               BufferedReader buff = new BufferedReader(file);
               boolean eof = false;
               String val0="";
               ResultSet rec = st.executeQuery("SELECT landings_hold_batch_seq.nextval FROM dual");
                    while(rec.next())
                    { val0 = rec.getString(1); }
                    cnt=0;
                    while (!eof)
                    { String line = buff.readLine();
                    if (line == null)
                    { eof = true; }
                         else
                         { cnt = cnt+1;
                              st1 = new StringTokenizer(line,",");
                              val1 = st1.nextToken();
                              val2 = st1.nextToken();
                              val3 = st1.nextToken();
                              val4 = st1.nextToken();
                              val5 = st1.nextToken();
                              val6 = st1.nextToken();
                              val7 = st1.nextToken();
                              val8 = st1.nextToken();
                              val9 = st1.nextToken();
                              val10 = st1.nextToken();
                              val11 = st1.nextToken();
                              val12 = st1.nextToken();
                              val13 = st1.nextToken();
                              val14 = st1.nextToken();
                              val15 = st1.nextToken();
                              val16 = st1.nextToken();
                              val17 = st1.nextToken();
                              val18 = st1.nextToken();
                              val19 = st1.nextToken();
                              val20 = st1.nextToken();
                              st.executeUpdate("INSERT INTO LANDINGS_HOLD (lh_id, lh_batch, supplier_dr_id, supplier_unique_id, supplier_dealer_id, supplier_cf_id, supplier_vessel_id, unload_year, unload_month, unload_day, state_code, county_code, port_code, itis_code, market, grade, reported_quantity, unit_measure, dollars, lh_loaddt, lh_loadlive, purch_year, purch_month, purch_day)" +
                    "VALUES (0,'"+val0+"','"+val1+"',"+val2+",'"+val3+"','"+val4+"','"+val5+"',"+val6+","+val7+","+val8+",'"+val9+"','"+val10+"','"+val11+"','"+val12+"','"+val13+"','"+val14+"',"+val15+",'"+val16+"',"+val17+",SYSDATE,NULL,"+val18+","+val19+","+val20+")");
                         } // while else end
                    } // parent while end
                    FileReader in = new FileReader(inputFile);
                    FileWriter out = new FileWriter(outputFile);
int c;
                    while ((c = in.read()) != -1)
                    { out.write((char)c); }
                    in.close();
                    out.close();
                    outFile.write(System.getProperty("line.separator"));
                    outFile.write("Number of records inserted - "+cnt);
                    outFile.write(System.getProperty("line.separator"));
                    outFile.write("Copied upload file to archive directory");
                    outFile.write(System.getProperty("line.separator"));
                    outFile.write(f+"/"+s[i]+" - Has been removed from upload directory");
                    buff.close();
                    inputFile.delete();
               } // for end
               outFile.write(System.getProperty("line.separator"));
               outFile.write("Upload Complete...NO ERRORS");
               outFile.write(System.getProperty("line.separator"));
               outFile.write("*************************************************************");
               outFile.write(System.getProperty("line.separator"));
               conn.close();
          } // if end
          else
          { outFile.write("No files to process"); }
          outFile.flush();
          outFile.close();
          } // try end.
          catch(Exception e)
          { FileWriter errFile = new FileWriter("C://RIFIS/log/errfile.txt", true);
          errFile.write(System.getProperty("line.separator"));
          errFile.write("ALERT....ALERT....ALERT");
          errFile.write(System.getProperty("line.separator"));
          errFile.write("Error Occurred in ReadSource.java - RIFIS Upload");
          errFile.write(System.getProperty("line.separator"));
          errFile.write("My Error: " + e);
          errFile.write(System.getProperty("line.separator"));
          errFile.write("*************************************************************");
               errFile.flush();
               errFile.close();
          } // catch exception end.
     return "Hello from java";
     } //public msg block
     public ch06_03()

Since you didn't use code-formatting tags ([ code ] and [ /code ] without the spaces) it's kinda hard to look at it. But I'm sure it DID execute much more than just the return statement - maybe you're not closing a file or db connection, or maybe you're seeing a cached page, so it actually isn't executing ANYTHING on the server (is your browser set to never check for newer pages so it (almost) always returns from cache, for example?)

Error in XMLDiff Bean, System.exit() is being called in setFiles() ?

Similar Messages

Maybe you are looking for