Catching Runtime Exception

Is it good practice to catch High level Exception in the try block, this would also catch RuntimeException. My personal opinion is not to catch the Runtime Exception and let the JVM handle it. However if there is a need to catch specific Runtime Exception, code should be written for that.
try
// Your code
catch (Exception e)
e.printStackTrace()
}

I agree that runtime exceptions should generally not
be caught as they are mistakes of programmers.
But in order to debug a large project with hundreds of
classes it can be useful to do that anyways.
Any my big question is: how?
I tried to wrap the content of the main method in a
try / catch block hoping that I could catch all
exceptions not handled somewhere else.
But it didn't work.
I manually threw some exceptions somewhere in my GUI
and the main method wrapper didn't get them.
But the VM did and printed the exception message.
But I didn't want the VM to catch my exceptions. I
wanted to catch them myself at the lowest possible
point in my own classes.
And I thought that was the main method.
Can anyone help me?
Thank you
Matthias Klein
P.S. please excuse my improvable english; it's not my
mother tongue.AWT uses many different threads in your program that you never find out about unless something breaks. main(String arg[]) starts as the lowest possible point but, if you construct a Frame, Image, or certain other objects from the AWT package, AWT Threads automatically start over which you have little or no control.
Overall, I don't think it's actually possible to catch the Runtime Exceptions out of these Threads. The best this you can do about them is prevent them from happening.

Similar Messages

  • Catch Runtime Exceptions under 46C

    Hello experts,
    My programme executes a dynamic open sql and the requirement is, my programme should never result in an ABAP short dump.
    With ABAP release 610, I can catch class based exceptions like cx_sy_dynamic_osql_error, but under 46C, I can only use CATCH SYSTEM-EXCEPTIONS, but no sql exceptions can be found in the runtime error list, that means no sql exceptions are perceived as catchable runtime errors.
    Therefore, could you advise how I should handle the runtime exceptions and not cause the ABAP short dump, please?
    Thanks and best regards,
    James

    http://help.sap.com/saphelp_nw04/helpdata/en/a9/b8eef8fe9411d4b2ee0050dadfb92b/content.htm
    will TRY and the CATCH statement be of any use ?

  • CHECK V RUNTIME EXCEPTION

    Hi there
    What is the difference between a checked and runtime exception?

    All exceptions are checked and
    are required to be caught in a try-catch block unless
    they are descended from RuntimeException.
    You aren't required to catch runtime exceptions in a try-catch block while you are required to catch checked exceptions. Oh, really? I had a question like this when my company gave us a Java exam. Almost every one got that one wrong.
    The question was whether a thrown checked exception must eventually
    be caught and handled by the program.
    Consider this:
    public class ExcTest
      public static void main(String[] a)throws IOException
           throw new IOException();
    Here, a checked exception is thrown and not handled by the programmer.

  • Catchable Runtime Errors list (CATCH SYSTEM-EXCEPTIONS)?

    Hi All,
    I was just going through CATCH SYSTEM-EXCEPTIONS syntax. Could anyone give all the possible SAP existing Exceptions or kindly let me know how I can find in the system (4.6C) ?
    Thankss,
    Neeth

    Hi Vijay,
    Having read this post of yours, I couldn't help appreciating your modesty. And we hope to see much more active participation from your in this forum.
    By the way, you now have 50 points with just 22 posts. Now, can you keep up this ratio? Just try it. And you will know better
    Trying to pull your leg, anand mandalika.
    ========================================================
    And Nameeth,
    I really appreciate your coming back and rewarding the responses promptly. Please keep that up.
    Regards,
    Anand Mandalika.

  • Best Practice: JavaFX pattern for "Catching all Exceptions"

    Hi,
    what is on the current JavaFX Standard the best way to catch all Exceptions (centralized) within my JavaFX application...
    I read thread outside this Oracle Forum who recommend following:
    1. Thread.setDefaultUncaughtExceptionHandler(new MyExceptionHandler());
    --> catch all runtime exceptions
    2. http://stackoverflow.com/questions/12318861/javafx-2-catching-all-runtime-exceptions
    --> Implementing some source code who wrap the current GUI thread...
    3. I read something like:
    "JavaFX exception handling is almost identical to that in Java, apart from the fact that checked exceptions are handled in the same way as unchecked exceptions. This is good news for most Java programmers moving to JavaFX because you are no longer obliged to catch and handle exceptions."
    Sounds very good! But where/how can I do this ???
    Edited by: wschele on 19.02.2013 04:58
    Edited by: wschele on 19.02.2013 05:16

    No recommendation whats the best way to do it?
    Catching each Exception in different layers is boring ! :-(

  • How to handle runtime exceptions for sync scenario?

    Hi Experts,
       I have a synchronous scenario.
       Request :
       webservice -
    > sends input data -
    > PI -
    > SAP R/3 --BAPI
       Response:
       webservice -<---  PI <sends back any validation error or successfully processed message----- SAP R/3 --BAPI
       Here a webservice uses SOAP adapter to send input data to PI. While PI uses ABAP proxy to send data to SAP R/3.
       The problem is when the BAPI takes too long to process and resulting in timeout exception in PI. Is there some way we can catch this runtime exception in PI and send it to webservice as response?
       Please help!
    Thanks & Regards,
    Gopal

    Hi Gopal,
    as mentioned by otheres: the main issue is here to detect the reason for performance lack...
    >Is there some way we can catch this runtime exception in PI and send it to webservice as response?
    You can invoke a Business Process and open a sync / asyn Bridge. In the process call the FM synchronous and define an exception branch which you access in case of system failure. In the exception branch execute a transformation step to fill the response container with a corresponding error message.
    Regards,
    Udo

  • Throwing Runtime Exceptions from BPM. How?

    Hi !
    I want to make appear a red flag in the SXMB_MONI as a result of a custom condition inside a BPM. I tried with the control step, but it makes no "red flag".
    Should I make a transform step between 2 dummy message types with a UDF that throws the runtime exception there?? is there another way ?? We want a red flag as a result of a expired deadline while waiting a file adapter transport acknowledgement.
    Thanks !!
    Matias.

    Matias,
    As you said before you want the BPM to be errored out if it reach the deadline, am I right. In control step if u say cancel process it equivalent to logically deleting the work items, so obviously you will get an succesfull message. What I suggest you to do is in  Deadline branch - control branch select throw exception. The exception name has to be defined in Block level. So if you throw an exception it will look for the exception branch in the same block level if not the higher(super)block level, if it couldn't find the exception branch it will run out to error. Actually the exception branch is used to catch that exception and continue the rest of the process, so i think there is no need for defining the exception branch itself.
    Hope it helps you!!!
    Best regards,
    raj.

  • Write and read txt files and catch the exceptions

    hey everyone, im in a bit of a bind. im trying to set up this try catch statement. here is what i have for code so far.
    import java.util.Scanner;
    import java.io.*;
    public class Warning
        //   Reads student data (name, semester hours, quality points) from a
        //   text file, computes the GPA, then writes data to another file
        //   if the student is placed on academic warning.
        public static void main (String[] args)
         int creditHrs;         // number of semester hours earned
         double qualityPts;     // number of quality points earned
         double gpa;            // grade point (quality point) average
         String line, name, inputName = "students.dat";
         String outputName = "warning.dat";
         try
              Scanner FileScan1 = new Scanner (new File("students.dat"));
              // Set up scanner to input file
              // Set up the output file stream
              // Print a header to the output file
              outFile.println ();
              outFile.println ("Students on Academic Warning");
              outFile.println ();
              // Process the input file, one token at a time
              while (FileScan1.hasNext())//there is another line...
                  {               // Get the credit hours and quality points and
                   // determine if the student is on warning. If so,
                   // write the student data to the output file.
              // Close output file
         catch (FileNotFoundException exception)
              System.out.println ("The file " + inputName + " was not found.");
         catch (IOException exception)
              System.out.println (exception);
         catch (NumberFormatException e)
              System.out.println ("Format error in input file: " + e);
    }I am pretty sure the layout is good to go, but first and foremost that try statement is hanging me up. Could someone give me some suggestions about how i should set this up.
    i want to read in this students.dat file, then output another file called warning.dat.
    Thanks i really appreicate the help.

    no, i was really hoping to just see if the way it is
    set up it will be doable, that way i wouldn't be
    working on code that was impossiable to sort through
    properlyFair enough.
    One thing I'd suggest is that if you're really basically only going to be printing the exceptions, and since that is the top-level method (main) --
    I'd instead just add some "throws" clauses to main, get rid of the try/catch stuff, and just let the VM handle the exceptions for you. It will print them, just like you're doing, except that it will also print the stack traces, which you are not doing.
    If you're going to handle exceptions, it's better to actually do something about them rather than just print them - otherwise you might just as well let the runtime do that for you.

  • SQLJ runtime exception in 9.2.0.4

    Hi,
    I work on a software using oracle, java and SQLJ technology. Since we pass from oracle 8.1.6 to Oracle 9.2.0.4 we have some sqlj runtime exception. These exceptions are randoms, amazing as the same request with SQL*plus is working, and occurrs randomly in time so it works all the same ...
    examples (in bold the oracle exception text) :
    1/ Unable to define propagation alert iterator (this exception is an SQL one and catched within the program) : Invalid column name
    the sqlj command corresponding => #sql ppgAlertIter = { SELECT USER_LOGIN FROM ALERT WHERE SAFETY_EVENT_ID = :incId AND OCCURRENCE_ID = :occId AND USER_LOGIN IN ( SELECT USER_LOGIN FROM USERS WHERE ROLE_NAME <> :roleName) };
    all the column names are rights !!!!
    2/java.lang.NullPointerException at sqlj.runtime.ExecutionContext$OracleContext.oracleExecuteQuery(ExecutionContext.java:1585) at asmtdb.DBUser.getComponentUpdateTime(DBUser.java:882)
    here is a runtime exception (not catched) (this exception correpsonds to the SQLJ commqnd in example 3/)
    3/exception when getting component's update time : Unable to retrieve component's update time : expected 1 columns in select list but found 11
    the SQLJ command corresponding => #sql { SELECT TO_CHAR(UPDATE_TIME, 'DD/MM/YYYY HH24:MI:SS') INTO :updateTime FROM COMPONENT WHERE COMPONENT_NAME = :componentName };
    with SQL*plus no problems to have a result, more is that we have only 3 distinct columns, so why 11 ????
    Is anyone had already these kinds of troubleshootings ???
    Here is my environment :
    - HP-UX B.11.00 U 9000/785 (64 bits)
    - Oracle SQLJ Release 9.2.0.3.0 Production
    Copyright © 1997, 2003, Oracle Corporation. All Rights Reserved.
    Build version: 2.3.0.0 - Built on Feb 15, 2002
    IDE interface version: 9.2.0.3.0/2.3.0.0
    JDBC version: Oracle JDBC driver version 9.2 (9.2.0.3.0)
    SQLJ runtime: Oracle 9.2.0 for JDBC 8.1.7 or later/JDK 1.2.x - Built on Jul 21, 2003
    Java version: 1.4 (1.4.2.00)
    Chris

    Chris,
    The error messages are misleading. I'm only guessing, but from what you have posted, it looks like the problem is in the values you are supplying for your bind variables. It could be that the SQL parser thinks that a bind variable is a column name -- and, of-course, there is no such column name, hence the "Invalid column name" error. Do you know about P6Spy ? It captures the SQL with the bind variable values, so you see the exact SQL that is getting sent to Oracle.
    Good Luck,
    Avi.

  • Runtime exception for other than programming error.

    In a conversation the question arose whether it could be a case of throwing a runtime exception for anything other than a bug. The tutorial on oracle site says "These Usually Indicate programming bugs" leading to think that can be used in situations in which there is no bug.
    Anyone have a practical example of a runtime exception when there is no bug?
    Thanks.

    937643 wrote:
    Ok. But. Do you think that in these cases the use of a runtime exception could be considered a bad practice?That's actually a matter of some debate.
    On the one hand, Java has defined two major kinds of exceptions since the very beginning (unchecked exceptions, which are RuntimeException, Error, and their descendants; and checked exceptions which are everything else). The intended use of those was that checked exceptions should be for things that can normally go wrong in the execution of a program, even without a bug or without a major internal JVM error, such as a failed attempt to persist something or a network connection dropping--stuff that a programmer might normally be expected to deal with; while unchecked exceptions were created for things that a programmer would not normally handle in his code (except possibly at major architectural boundaries), like buggy code or an internal JVM failure.
    With the rule about having to catch or declare checked exceptions, but not unchecked ones, that makes it easy for programmers so say, "Okay, I know exactly what can go wrong here that I might be expected to handle and I can therefore choose what to do with it; there will be no surprises. But I don't have to deal with problems that are outside my normal responsibility, like somebody passing me a null when they shouldn't have." It gives a programmer a nice bit of control, and the ability to know he hasn't missed something, kind of like the type safety provided by a strongly typed language.
    At least that's the theory.
    In practice, most checked exceptions either just get bubbled up to the next layer (via a throws clause), or caught wrapped in a fairly generic layer-appropriate exception and rethrown. There's not a whole lot of use made of what checked exceptions provide, and there's a lot of ugly boilerplate code that doesn't do anything useful for the app but is just there to satisfy the compiler.
    So, some people think that checked exceptions are useless, or mostly useless, and favor unchecked exceptions in most or all cases. I believe that's part of the philosophy of Spring, but I'm not totally sure.
    The idea is that since most of the time you can't do anything about exceptions that might be thrown to you, it's wasteful and pointless to have all that code to catch and rethrow. In this viewpoint, it would be better if, for example, not providing a throws clause at all meant that you could throw any exception. Any given code can still catch specific exceptions that it knows it can handle, but we don't have to write a bunch of code notating something that we're not really doing anything about.
    Personally, I used to be totally in the checked exception camp. However, all the pointless boilerplate is wearing me down. I'm still not completely convinced though, and here's why: If I'm calling a method, I'd like to at least be able to see what might go wrong, so that I can decide how to deal with it. If all exceptions were unchecked, and the throws clause were optional, a conscientious developer could still provide it, and list the unchecked exceptions his method might throw to me, and/or he could document them in the javadoc comments. But a lot of developers won't do that, or even if they start to, as their method evolves, without the compiler to enforce it, they won't keep it up to date.
    So there are advantages to both approaches. I personally would to know that the information will always be available to me, but for the small percentage of the time where I actually use it (like handle one specific exception one way and some other exception differently), I'm not sure if it's worth the overhead.

  • Runtime Exception - Need Help

    Hi
    I have a simple BPEL process to test the exception handling. It basically consists of a Invoke to call a EJB and a catchAll around the invoke. If there is an exception due to the Target EJB not available , the catchAll catches the exception, but if there is a runtime exception thrown in the EJB such as a NullPointerException, the catchAll does not capture it and also i'm not able to even access the instance, the instance itself vanishes. I have included the detailed log below..
    can some one shed some light on this..?
    Thanks in advance
    Sam
    The log contains activities of creating a new instance from Dashboard and click on the 'Flow' in console
    &gt;&gt;&gt;&gt; Log Start &gt;&gt;&gt;&gt;
    &lt;2005-02-04 10:24:08,953&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::getConnecti
    on&gt; GOT CONNECTION 1
    &lt;2005-02-04 10:24:08,953&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::closeConnec
    tion&gt; CLOSE CONNECTION 0
    &lt;2005-02-04 10:24:08,953&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::getConnecti
    on&gt; GOT CONNECTION 1
    &lt;2005-02-04 10:24:08,953&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::closeConnec
    tion&gt; CLOSE CONNECTION 0
    &lt;2005-02-04 10:24:08,968&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;WSDLSchemaUtil::getInputParameters&gt; In
    put parameter name payload parameter type {http://acm.org/samples}EHT1Request
    &lt;2005-02-04 10:24:09,046&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::getConnecti
    on&gt; GOT TX CONNECTION 1
    &lt;2005-02-04 10:24:09,062&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;BaseDeliveryPersistenceAdaptor
    ::storeInvoke&gt; Compressed message bytes from 850 to 381
    &lt;2005-02-04 10:24:09,062&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::closeConnec
    tion&gt; CLOSE TX CONNECTION 0
    &lt;2005-02-04 10:24:09,109&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;Dispatcher::insert&gt; Receiv
    ed batch message, 1 messages [invoke instance message aacf889e30f5e83a:125e791:101ddf7208b:-7ffb]
    &lt;2005-02-04 10:24:09,109&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;BaseDispatchSet::receive&gt;
    Receiving message [invoke instance message aacf889e30f5e83a:125e791:101ddf7208b:-7ffb] for set invok
    e
    &lt;2005-02-04 10:24:09,109&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;BaseDispatchSet::receive&gt;
    Receiving message [] for set engine
    &lt;2005-02-04 10:24:09,109&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;Dispatcher::receive&gt; Alloc
    ating new thread; pending threads: 1, active threads: 0, total: 0
    &lt;2005-02-04 10:24:09,171&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;DispatcherBean::init&gt; Done
    initializing dispatcher queue 'java:comp/env/jms/collaxa/BPELWorkerQueue'
    &lt;2005-02-04 10:24:09,187&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;InvokeDispatchSet::fetchSc
    heduled&gt; Fetched message invoke instance message aacf889e30f5e83a:125e791:101ddf7208b:-7ffb from inv
    oke queue for processing
    &lt;2005-02-04 10:24:09,234&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;DispatcherBean::send&gt; Sent
    message to queue java:comp/env/jms/collaxa/BPELWorkerQueue
    &lt;2005-02-04 10:24:09,234&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;Dispatcher::insert&gt; Receiv
    ed batch message, 0 messages []
    &lt;2005-02-04 10:24:09,250&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;InvokeInstanceMessageHandl
    er::handle&gt; Processing invoke instance message for domain default
    &lt;2005-02-04 10:24:09,250&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::getConnecti
    on&gt; GOT TX CONNECTION 1
    &lt;2005-02-04 10:24:09,250&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;BaseDispatchSet::receive&gt;
    Receiving message [] for set invoke
    &lt;2005-02-04 10:24:09,250&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;BaseDispatchSet::receive&gt;
    Receiving message [] for set engine
    &lt;2005-02-04 10:24:09,250&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;Dispatcher::receive&gt; Alloc
    ating new thread; pending threads: 1, active threads: 1, total: 1
    &lt;2005-02-04 10:24:09,250&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;DispatcherBean::send&gt; Sent
    message to queue java:comp/env/jms/collaxa/BPELWorkerQueue
    &lt;2005-02-04 10:24:09,250&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;BaseDispatchSet::receive&gt;
    Receiving message remove dispatcher bean message aacf889e30f5e83a:125e791:101ddf7208b:-7ffa for set
    system
    &lt;2005-02-04 10:24:09,250&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;Dispatcher::receive&gt; Alloc
    ating new thread; pending threads: 1, active threads: 1, total: 2
    &lt;2005-02-04 10:24:09,265&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;DispatcherBean::send&gt; Sent
    message to queue java:comp/env/jms/collaxa/BPELWorkerQueue
    &lt;2005-02-04 10:24:09,281&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;SystemDispatchSet::fetchSc
    heduled&gt; Fetched message remove dispatcher bean message aacf889e30f5e83a:125e791:101ddf7208b:-7ffa f
    rom system queue for processing
    &lt;2005-02-04 10:24:09,281&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;RemoveMessageHandler::hand
    le&gt; Processing remove message for ticket aacf889e30f5e83a:125e791:101ddf7208b:-7ffa
    &lt;2005-02-04 10:24:09,281&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;BaseDispatchSet::acknowled
    ge&gt; Acknowledged message remove dispatcher bean message aacf889e30f5e83a:125e791:101ddf7208b:-7ffa
    &lt;2005-02-04 10:24:09,296&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;BaseInvokeHandler::load&gt; Loade
    d message bytes, compressed 381 , uncompressed 850
    &lt;2005-02-04 10:24:09,312&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.delivery&gt; &lt;InvokeCache::remove&gt; Remov
    ing cache entry for message aacf889e30f5e83a:125e791:101ddf7208b:-7ffb
    &lt;2005-02-04 10:24:09,375&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;DOMElement__CXPM::__create&gt; Creating n
    ormal element EHT1Request, state=0
    &lt;2005-02-04 10:24:09,375&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;DomSerializerUtil::loadElement&gt; Loaded
    element EHT1Request size=238
    &lt;2005-02-04 10:24:09,390&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::getConnecti
    on&gt; GOT TX CONNECTION 2
    &lt;2005-02-04 10:24:09,390&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::closeConnec
    tion&gt; CLOSE TX CONNECTION 1
    &lt;2005-02-04 10:24:09,421&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::createInstance&gt; Created
    cube instance '2701' from process 'EHT1' (revision '1.0')
    &lt;2005-02-04 10:24:09,500&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;MethodCubeBlock::activate&gt; Create m
    ethod scope 'BpPrc0.1' in block 'BpPrc0'
    &lt;2005-02-04 10:24:09,500&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;MethodCubeBlock::activate&gt; Method n
    ame:processTransaction type: not-supported
    &lt;2005-02-04 10:24:09,515&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::invokeMethod&gt; Invoking
    method 'initiate' on cube instance '2701'
    &lt;2005-02-04 10:24:09,515&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Managing s
    cope 'BpPrc0.1' on cube instance '2701'
    &lt;2005-02-04 10:24:09,531&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Can activa
    te block 'BpTry0' with scope 'BpPrc0.1'
    &lt;2005-02-04 10:24:09,531&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELExecution::EHT1&gt; entering
    &lt;scope&gt; at line [no line]
    &lt;2005-02-04 10:24:09,531&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELExecution::EHT1&gt; entering
    &lt;scope&gt; at line [no line]
    &lt;2005-02-04 10:24:09,531&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;BaseCubeBlock::activate&gt; Create sco
    pe 'BpTry0.2' in block 'BpTry0'
    &lt;2005-02-04 10:24:09,531&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Can activa
    te block 'BpSeq0' with scope 'BpTry0.2'
    &lt;2005-02-04 10:24:09,531&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELExecution::EHT1&gt; entering
    &lt;sequence&gt; at line 35
    &lt;2005-02-04 10:24:09,531&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELExecution::EHT1&gt; entering
    &lt;sequence&gt; at line 35
    &lt;2005-02-04 10:24:09,531&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;SensorManager::doCallback&gt; queried
    map w/key main
    &lt;2005-02-04 10:24:09,531&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;BaseCubeBlock::activate&gt; Create sco
    pe 'BpSeq0.3' in block 'BpSeq0'
    &lt;2005-02-04 10:24:09,546&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Can activa
    te node 'BpRcv0' with scope 'BpSeq0.3'
    &lt;2005-02-04 10:24:09,546&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Scheduling
    workitem 2701-BpRcv0-BpSeq0.3-1 to be performed
    &lt;2005-02-04 10:24:09,546&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Done manag
    ing scope 'BpPrc0.1'
    &lt;2005-02-04 10:24:09,546&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;DispatchHelper::sendMemory
    &gt; Dispatching in-memory request, [workitem perform message 2701-BpRcv0-BpSeq0.3-1]
    &lt;2005-02-04 10:24:09,546&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;PerformMessageHandler::han
    dleLocal&gt; Processing workitem perform message 2701-BpRcv0-BpSeq0.3-1 for domain default
    &lt;2005-02-04 10:24:09,562&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::handleWorkItem&gt; Attempt
    ing to handle workitem 2701-BpRcv0-BpSeq0.3-1 with transition 0
    &lt;2005-02-04 10:24:09,562&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::performActivity&gt; Perfor
    ming workitem '2701-BpRcv0-BpSeq0.3-1'
    &lt;2005-02-04 10:24:09,562&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;SensorManager::doCallback&gt; queried
    map w/key receiveInput
    &lt;2005-02-04 10:24:09,562&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELEntryReceiveWMP::EHT1&gt; exe
    cuting &lt;receive&gt; at line 39
    &lt;2005-02-04 10:24:09,562&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELEntryReceiveWMP::EHT1&gt; set
    variable 'input' to be readOnly.
    &lt;2005-02-04 10:24:09,562&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;SensorManager::doCallback&gt; queried
    map w/key input
    &lt;2005-02-04 10:24:09,578&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;DOMElement::toXML&gt; Converting to XML E
    HT1Request, state= 3
    &lt;2005-02-04 10:24:09,578&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;DOMElement__CXPM::__toXML&gt; Converting
    element input to xml, state=0
    &lt;2005-02-04 10:24:09,578&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;DOMElement__CXPM::__toXML&gt; Converting
    element input uri http://acm.org/samples to xml
    &lt;2005-02-04 10:24:09,593&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;SensorManager::doCallback&gt; queried
    map w/key receiveInput
    &lt;2005-02-04 10:24:09,593&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::performActivity&gt; Is per
    former 2701-BpRcv0-BpSeq0.3-1 idempotent? true
    &lt;2005-02-04 10:24:09,593&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::checkBlockConditions&gt; W
    orkitem '2701-BpRcv0-BpSeq0.3-1' has been marked as complete
    &lt;2005-02-04 10:24:09,593&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::finalizeActivity&gt; Attem
    pting to finalize workitem '2701-BpRcv0-BpSeq0.3-1'
    &lt;2005-02-04 10:24:09,593&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::checkManageScope&gt; Found
    highest dirty scope 'BpPrc0.1'
    &lt;2005-02-04 10:24:09,593&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Managing s
    cope 'BpPrc0.1' on cube instance '2701'
    &lt;2005-02-04 10:24:09,593&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Can activa
    te block 'BpScp0' with scope 'BpSeq0.3'
    &lt;2005-02-04 10:24:09,593&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELExecution::EHT1&gt; entering
    &lt;scope&gt; at line 44
    &lt;2005-02-04 10:24:09,593&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;SensorManager::doCallback&gt; queried
    map w/key scope-1
    &lt;2005-02-04 10:24:09,609&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;BaseCubeBlock::activate&gt; Create sco
    pe 'BpScp0.4' in block 'BpScp0'
    &lt;2005-02-04 10:24:09,609&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Can activa
    te block 'BpTry1' with scope 'BpScp0.4'
    &lt;2005-02-04 10:24:09,609&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELExecution::EHT1&gt; entering
    &lt;scope&gt; at line [no line]
    &lt;2005-02-04 10:24:09,609&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELExecution::EHT1&gt; entering
    &lt;scope&gt; at line [no line]
    &lt;2005-02-04 10:24:09,609&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;BaseCubeBlock::activate&gt; Create sco
    pe 'BpTry1.5' in block 'BpTry1'
    &lt;2005-02-04 10:24:09,609&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Can activa
    te block 'BpSeq1' with scope 'BpTry1.5'
    &lt;2005-02-04 10:24:09,609&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELExecution::EHT1&gt; entering
    &lt;sequence&gt; at line 52
    &lt;2005-02-04 10:24:09,609&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELExecution::EHT1&gt; entering
    &lt;sequence&gt; at line 52
    &lt;2005-02-04 10:24:09,609&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;BaseCubeBlock::activate&gt; Create sco
    pe 'BpSeq1.6' in block 'BpSeq1'
    &lt;2005-02-04 10:24:09,625&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Can activa
    te node 'BpAss0' with scope 'BpSeq1.6'
    &lt;2005-02-04 10:24:09,625&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Scheduling
    workitem 2701-BpAss0-BpSeq1.6-1 to be performed
    &lt;2005-02-04 10:24:09,625&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Done manag
    ing scope 'BpPrc0.1'
    &lt;2005-02-04 10:24:09,625&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::performActivity&gt; Done p
    erforming workitem '2701-BpRcv0-BpSeq0.3-1'
    &lt;2005-02-04 10:24:09,625&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::handleWorkItem&gt; Done ha
    ndling workitem 2701-BpRcv0-BpSeq0.3-1
    &lt;2005-02-04 10:24:09,625&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;PerformMessageHandler::han
    dleLocal&gt; Processing workitem perform message 2701-BpAss0-BpSeq1.6-1 for domain default
    &lt;2005-02-04 10:24:09,640&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::handleWorkItem&gt; Attempt
    ing to handle workitem 2701-BpAss0-BpSeq1.6-1 with transition 0
    &lt;2005-02-04 10:24:09,640&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::performActivity&gt; Perfor
    ming workitem '2701-BpAss0-BpSeq1.6-1'
    &lt;2005-02-04 10:24:09,640&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;SensorManager::doCallback&gt; queried
    map w/key initIS
    &lt;2005-02-04 10:24:09,640&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELAssignWMP::EHT1&gt; executing
    &lt;copy&gt; at line 52
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;XPathUtil::initXPath&gt; namespaceMapping
    is: {bpws=http://schemas.xmlsoap.org/ws/2003/03/business-process/, tns=http://acm.org/samples, xsd=
    http://www.w3.org/2001/XMLSchema, bpelx=http://schemas.oracle.com/bpel/extension, ora=http://schemas
    .oracle.com/xpath/extension, nsxml0=http://www.emergingaspects.com/service/EXHT}
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;XPathUtil::evaluate&gt; XPathQuery[string
    ("NOT OK")], XPath Result: class=java.lang.String value=NOT OK
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;PersistenceManager::copy( Obje
    ct )&gt; copying %jS
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;SensorManager::doCallback&gt; queried
    map w/key invokeStatus
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;SensorManager::doCallback&gt; queried
    map w/key initIS
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::performActivity&gt; Is per
    former 2701-BpAss0-BpSeq1.6-1 idempotent? true
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::checkBlockConditions&gt; W
    orkitem '2701-BpAss0-BpSeq1.6-1' has been marked as complete
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::finalizeActivity&gt; Attem
    pting to finalize workitem '2701-BpAss0-BpSeq1.6-1'
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::checkManageScope&gt; Found
    highest dirty scope 'BpPrc0.1'
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Managing s
    cope 'BpPrc0.1' on cube instance '2701'
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Can activa
    te node 'BpInv0' with scope 'BpSeq1.6'
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Scheduling
    workitem 2701-BpInv0-BpSeq1.6-2 to be performed
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Done manag
    ing scope 'BpPrc0.1'
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::performActivity&gt; Done p
    erforming workitem '2701-BpAss0-BpSeq1.6-1'
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::handleWorkItem&gt; Done ha
    ndling workitem 2701-BpAss0-BpSeq1.6-1
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;PerformMessageHandler::han
    dleLocal&gt; Processing workitem perform message 2701-BpInv0-BpSeq1.6-2 for domain default
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::handleWorkItem&gt; Attempt
    ing to handle workitem 2701-BpInv0-BpSeq1.6-2 with transition 0
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::performActivity&gt; Perfor
    ming workitem '2701-BpInv0-BpSeq1.6-2'
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;SensorManager::doCallback&gt; queried
    map w/key invokeEHTS
    &lt;2005-02-04 10:24:09,671&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELInvokeWMP::EHT1&gt; executing
    &lt;invoke&gt; at line 57
    &lt;2005-02-04 10:24:09,703&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.ws&gt; &lt;WSInvocationManager::invoke&gt; operation:
    doExceptionHandlingTest
    &lt;2005-02-04 10:24:09,703&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.ws&gt; &lt;WSInvocationManager::invoke&gt; inputConta
    iner: {payload=&lt;payload xmlns="http://www.emergingaspects.com/service/EXHT"/&gt;}
    &lt;2005-02-04 10:24:09,703&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.ws&gt; &lt;WSInvocationManager::invoke&gt; callProps:
    {is-initial-call=true, parentId=2701, syncPersistMode=null, process-id=EHT1, rootId=2701, conversat
    ionId=bpel://localhost/default/EHT1~1.0/2701-BpInv0-BpSeq1.6-2, location=null, priority=3, work-item
    -key=2701-BpInv0-BpSeq1.6-2, domain-id=default, revision-tag=1.0}
    &lt;2005-02-04 10:24:09,718&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.ws&gt; &lt;WSDLManager::getWSDL&gt; registered wsdl a
    t http://sampc:9700/orabpel/default/EHT1/ExceptionHandlingTestService.wsdl
    &lt;2005-02-04 10:24:09,718&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.ws&gt; &lt;WSDLManager::getWSDL&gt; got wsdl at: http
    ://sampc:9700/orabpel/default/EHT1/ExceptionHandlingTestService.wsdl
    &lt;2005-02-04 10:24:09,718&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.ws&gt; &lt;WSInvocationManager::invoke&gt; def is htt
    p://sampc:9700/orabpel/default/EHT1/ExceptionHandlingTestService.wsdl
    &lt;2005-02-04 10:24:09,718&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.ws&gt; &lt;WSIFInvocationHandler::invoke&gt; opName=d
    oExceptionHandlingTestportTypeQn={http://www.emergingaspects.com/service/EXHT}EXHTServiceserviceQn={
    http://www.emergingaspects.com/service/EXHT}EXHTService
    &lt;2005-02-04 10:24:09,859&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;DOMSerializerUtil::binaryDeepCopy&gt; Beg
    in binary deep copy for payload
    &lt;2005-02-04 10:24:09,859&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;DOMElement__CXPM::__deepCopy&gt; Deep cop
    ying payload, uri=http://www.emergingaspects.com/service/EXHT, state=0
    &lt;2005-02-04 10:24:09,890&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;DOMElement__CXPM::__create&gt; Creating n
    ormal element payload, state=0
    &lt;2005-02-04 10:24:09,890&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;DOMSerializerUtil::binaryDeepCopy&gt; Don
    e binary deep copy for payload
    WSIF0005E: An error occurred when invoking the method 'doExceptionHandlingTest'. ('EJB')
    &lt;2005-02-04 10:24:09,953&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.ws&gt; &lt;WSIFInvocationHandler::invoke&gt; Fault ha
    ppenned
    javax.transaction.TransactionRolledbackException: EJB Exception: : java.lang.NullPointerException
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean.doExceptionHandlingTest(Excepti
    onHandlingTestEJBBean.java:28)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl.doExceptionHandli
    ngTest(ExceptionHandlingTestEJBBean_d9oiel_EOImpl.java:46)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl_WLSkel.invoke(Unk
    nown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    ; nested exception is:
    java.lang.NullPointerException
    at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl_812_WLStub.doExce
    ptionHandlingTest(Unknown Source)
    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.collaxa.cube.ws.wsif.providers.ejb.WSIFOperation_EJB.executeRequestResponseOperation(
    WSIFOperation_EJB.java:1071)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:392)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:321)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:143)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:569)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:299)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:182)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3447)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1824)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(Perfo
    rmMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:87
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:144)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5531)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1219)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at com.collaxa.cube.engine.bean.DeliveryBean_uhics8_ELOImpl.handleInvoke(DeliveryBean_uhics8
    _ELOImpl.java:274)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(Invok
    eInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:64)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
    at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Caused by: java.lang.NullPointerException
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean.doExceptionHandlingTest(Excepti
    onHandlingTestEJBBean.java:28)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl.doExceptionHandli
    ngTest(ExceptionHandlingTestEJBBean_d9oiel_EOImpl.java:46)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl_WLSkel.invoke(Unk
    nown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    ... 2 more
    &lt;2005-02-04 10:24:09,953&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.ws&gt; &lt;BPELInvokeWMP::__invoke&gt; Caught RemoteE
    xception
    orabpel.apache.wsif.WSIFException: Operation failed!; nested exception is:
    javax.transaction.TransactionRolledbackException: EJB Exception: : java.lang.NullPointerExce
    ption
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean.doExceptionHandlingTest(Excepti
    onHandlingTestEJBBean.java:28)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl.doExceptionHandli
    ngTest(ExceptionHandlingTestEJBBean_d9oiel_EOImpl.java:46)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl_WLSkel.invoke(Unk
    nown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    ; nested exception is:
    java.lang.NullPointerException
    at com.collaxa.cube.ws.wsif.providers.ejb.WSIFOperation_EJB.executeRequestResponseOperation(
    WSIFOperation_EJB.java:1207)
    at com.collaxa.cube.ws.WSIFInvocationHandler.invoke(WSIFInvocationHandler.java:392)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:321)
    at com.collaxa.cube.ws.WSInvocationManager.invoke(WSInvocationManager.java:143)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:569)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:299)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:182)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3447)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1824)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(Perfo
    rmMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:87
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:144)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5531)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1219)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at com.collaxa.cube.engine.bean.DeliveryBean_uhics8_ELOImpl.handleInvoke(DeliveryBean_uhics8
    _ELOImpl.java:274)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(Invok
    eInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:64)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
    at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Caused by: javax.transaction.TransactionRolledbackException: EJB Exception: : java.lang.NullPointerE
    xception
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean.doExceptionHandlingTest(Excepti
    onHandlingTestEJBBean.java:28)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl.doExceptionHandli
    ngTest(ExceptionHandlingTestEJBBean_d9oiel_EOImpl.java:46)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl_WLSkel.invoke(Unk
    nown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    ; nested exception is:
    java.lang.NullPointerException
    at weblogic.rjvm.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:108)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:284)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:244)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl_812_WLStub.doExce
    ptionHandlingTest(Unknown Source)
    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.collaxa.cube.ws.wsif.providers.ejb.WSIFOperation_EJB.executeRequestResponseOperation(
    WSIFOperation_EJB.java:1071)
    ... 27 more
    Caused by: java.lang.NullPointerException
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean.doExceptionHandlingTest(Excepti
    onHandlingTestEJBBean.java:28)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl.doExceptionHandli
    ngTest(ExceptionHandlingTestEJBBean_d9oiel_EOImpl.java:46)
    at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl_WLSkel.invoke(Unk
    nown Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
    at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
    ... 2 more
    &lt;2005-02-04 10:24:09,968&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;bpel.p0.BPEL_BIN$$BPELC_BpInv0::per
    form&gt; error thrown
    com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}bindingFault
    messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage}
    parts: {{summary=Operation failed!; nested exception is:
            javax.transaction.TransactionRolledbackException: EJB Exception: : java.lang.NullPointerExce
    ption
            at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean.doExceptionHandlingTest(Excepti
    onHandlingTestEJBBean.java:28)
            at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl.doExceptionHandli
    ngTest(ExceptionHandlingTestEJBBean_d9oiel_EOImpl.java:46)
            at com.ema.bpel.test.exceptions.ExceptionHandlingTestEJBBean_d9oiel_EOImpl_WLSkel.invoke(Unk
    nown Source)
            at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:477)
            at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:108)
            at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:420)
            at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:353)
            at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:144)
            at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:415)
            at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
            at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
            at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    ; nested exception is:
            java.lang.NullPointerException}}
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__invoke(BPELInvokeWMP.java:604)
    at com.collaxa.cube.engine.ext.wmp.BPELInvokeWMP.__executeStatements(BPELInvokeWMP.java:299)
    at com.collaxa.cube.engine.ext.wmp.BPELActivityWMP.perform(BPELActivityWMP.java:182)
    at com.collaxa.cube.engine.CubeEngine.performActivity(CubeEngine.java:3447)
    at com.collaxa.cube.engine.CubeEngine.handleWorkItem(CubeEngine.java:1824)
    at com.collaxa.cube.engine.dispatch.message.instance.PerformMessageHandler.handleLocal(Perfo
    rmMessageHandler.java:75)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleLocalMessage(DispatchHelper.java:87
    at com.collaxa.cube.engine.dispatch.DispatchHelper.sendMemory(DispatchHelper.java:144)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5531)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1219)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at com.collaxa.cube.engine.bean.DeliveryBean_uhics8_ELOImpl.handleInvoke(DeliveryBean_uhics8
    _ELOImpl.java:274)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(Invok
    eInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:64)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
    at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    &lt;2005-02-04 10:24:09,968&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;SensorManager::doCallback&gt; queried
    map w/key invokeEHTS
    &lt;2005-02-04 10:24:09,968&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;SensorManager::doCallback&gt; queried
    map w/key {http://schemas.oracle.com/bpel/extension}bindingFault
    &lt;2005-02-04 10:24:09,968&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::performActivity&gt; Is per
    former 2701-BpInv0-BpSeq1.6-2 idempotent? false
    &lt;2005-02-04 10:24:09,968&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::checkBlockConditions&gt; W
    orkitem '2701-BpInv0-BpSeq1.6-2' has been marked as complete
    &lt;2005-02-04 10:24:09,984&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::finalizeActivity&gt; Attem
    pting to finalize workitem '2701-BpInv0-BpSeq1.6-2'
    &lt;2005-02-04 10:24:09,984&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::finalizeActivity&gt; Caugh
    t business exception at block 'BpTry1', rolling back
    &lt;2005-02-04 10:24:09,984&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::forceCompleteScope&gt; Is
    instance faulted? true
    &lt;2005-02-04 10:24:09,984&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::forceCompleteScopeTree&gt;
    Forcing to complete scope rooted at 'BpTry1.5'
    &lt;2005-02-04 10:24:10,000&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;BaseWorkItemPersistenceAdaptor
    ::load&gt; Skipping database load ... found workitems
    &lt;2005-02-04 10:24:10,000&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::closeActivity&gt; Workitem
    2701-BpInv0-BpSeq1.6-2 is faulted ... skipping cancel
    &lt;2005-02-04 10:24:10,000&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.agents&gt; &lt;ExpirationAgent::unscheduleW
    orkItem&gt; Removing work item 2701-BpInv0-BpSeq1.6-2 from expiration scheduler
    &lt;2005-02-04 10:24:10,000&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::checkExpirable&gt; Removin
    g work item 2701-BpInv0-BpSeq1.6-2 from expiration agent
    &lt;2005-02-04 10:24:10,000&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;ForceCompleteTreeIterator::apply&gt; C
    ompleting scope 'BpTry1.5'
    &lt;2005-02-04 10:24:10,000&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;ForceCompleteTreeIterator::apply&gt; C
    ompleting scope 'BpSeq1.6'
    &lt;2005-02-04 10:24:10,031&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::forceCompleteScopeTree&gt;
    Done forced complete scope rooted at 'BpTry1.5'
    &lt;2005-02-04 10:24:10,031&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::checkManageScope&gt; Found
    highest dirty scope 'BpPrc0.1'
    &lt;2005-02-04 10:24:10,031&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Managing s
    cope 'BpPrc0.1' on cube instance '2701'
    &lt;2005-02-04 10:24:10,031&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Can activa
    te block 'BpCAl0' with scope 'BpScp0.4'
    &lt;2005-02-04 10:24:10,031&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELExecution::EHT1&gt; entering
    &lt;catchAll&gt; at line 48
    &lt;2005-02-04 10:24:10,031&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.bpel&gt; &lt;BPELExecution::EHT1&gt; entering
    &lt;catchAll&gt; at line 48
    &lt;2005-02-04 10:24:10,031&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;BaseCubeBlock::activate&gt; Create sco
    pe 'BpCAl0.7' in block 'BpCAl0'
    &lt;2005-02-04 10:24:10,031&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Can activa
    te node 'BpWai0' with scope 'BpCAl0.7'
    &lt;2005-02-04 10:24:10,031&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;XPathUtil::initXPath&gt; namespaceMapping
    is: {bpws=http://schemas.xmlsoap.org/ws/2003/03/business-process/, tns=http://acm.org/samples, xsd=
    http://www.w3.org/2001/XMLSchema, bpelx=http://schemas.oracle.com/bpel/extension, ora=http://schemas
    .oracle.com/xpath/extension, nsxml0=http://www.emergingaspects.com/service/EXHT}
    &lt;2005-02-04 10:24:10,031&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.xml&gt; &lt;XPathUtil::evaluate&gt; XPathQuery['PT30S
    '], XPath Result is: class java.lang.String
    &lt;2005-02-04 10:24:10,031&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.agents&gt; &lt;ExpirationAgent::unscheduleW
    orkItem&gt; Removing work item 2701-BpWai0-BpCAl0.7-1 from expiration scheduler
    &lt;2005-02-04 10:24:10,125&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.agents&gt; &lt;ExpirationScheduler::schedul
    e&gt; Work item 2701-BpWai0-BpCAl0.7-1 scheduled for Fri Feb 04 10:24:40 EST 2005
    &lt;2005-02-04 10:24:10,125&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Scheduling
    workitem 2701-BpWai0-BpCAl0.7-1 to be performed
    &lt;2005-02-04 10:24:10,125&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::manageScope&gt; Done manag
    ing scope 'BpPrc0.1'
    &lt;2005-02-04 10:24:10,125&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::performActivity&gt; Done p
    erforming workitem '2701-BpInv0-BpSeq1.6-2'
    &lt;2005-02-04 10:24:10,125&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::handleWorkItem&gt; Done ha
    ndling workitem 2701-BpInv0-BpSeq1.6-2
    &lt;2005-02-04 10:24:10,125&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;DispatchHelper::sendMemory
    &gt; In-memory false ... stop processing in-memory
    &lt;2005-02-04 10:24:10,125&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine&gt; &lt;CubeEngine::store&gt; Initial request
    ... storing instance 2701 to datastore
    &lt;2005-02-04 10:24:10,125&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;CubeInstancePersistenceMgr::st
    ore&gt; Storing instance 2701 to datastore
    &lt;BaseCubeSessionBean::logError&gt; Error while invoking bean "delivery": Cannot insert audit trail.
    The process domain was unable to insert the current log entries for the instance "2701" to the audit
    trail table. The exception reported is: The transaction is no longer active - status: 'Marked roll
    back. [Reason=java.lang.NullPointerException]'. No further JDBC access is allowed within this transa
    ction.
    Please check that the machine hosting the datasource is physically connected to the network. Otherw
    ise, check that the datasource connection parameters (user/password) is currently valid.
    sql statement: INSERT INTO audit_trail( cikey, domain_ref, count_id, block, block_csize, block_usiz
    e, log ) VALUES( ?, ?, ?, ?, ?, ?, ? )
    &lt;2005-02-04 10:24:10,187&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::closeConnec
    tion&gt; CLOSE TX CONNECTION 0
    &lt;2005-02-04 10:24:10,250&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;DispatchHelper::handleMess
    age&gt; failed to handlerMessage
    ORABPEL-04004
    Cannot insert audit trail.
    The process domain was unable to insert the current log entries for the instance "2701" to the audit
    trail table. The exception reported is: The transaction is no longer active - status: 'Marked roll
    back. [Reason=java.lang.NullPointerException]'. No further JDBC access is allowed within this transa
    ction.
    Please check that the machine hosting the datasource is physically connected to the network. Otherw
    ise, check that the datasource connection parameters (user/password) is currently valid.
    sql statement: INSERT INTO audit_trail( cikey, domain_ref, count_id, block, block_csize, block_usiz
    e, log ) VALUES( ?, ?, ?, ?, ?, ?, ? )
    at com.collaxa.cube.engine.adaptors.oracle.AuditTrailPersistenceAdaptor$TrailHandler.store(A
    uditTrailPersistenceAdaptor.java:283)
    at com.collaxa.cube.engine.adaptors.common.BaseAuditTrailPersistenceAdaptor.store(BaseAuditT
    railPersistenceAdaptor.java:134)
    at com.collaxa.cube.engine.adaptors.oracle.AuditTrailPersistenceAdaptor.store(AuditTrailPers
    istenceAdaptor.java:62)
    at com.collaxa.cube.engine.data.AuditTrailPersistenceMgr.store(AuditTrailPersistenceMgr.java
    :239)
    at com.collaxa.cube.engine.adaptors.common.BaseCubeInstancePersistenceAdaptor.store(BaseCube
    InstancePersistenceAdaptor.java:466)
    at com.collaxa.cube.engine.adaptors.oracle.CubeInstancePersistenceAdaptor.store(CubeInstance
    PersistenceAdaptor.java:74)
    at com.collaxa.cube.engine.data.CubeInstancePersistenceMgr.store(CubeInstancePersistenceMgr.
    java:307)
    at com.collaxa.cube.engine.CubeEngine.store(CubeEngine.java:5295)
    at com.collaxa.cube.engine.CubeEngine.endRequest(CubeEngine.java:5540)
    at com.collaxa.cube.engine.CubeEngine.createAndInvoke(CubeEngine.java:1219)
    at com.collaxa.cube.engine.delivery.DeliveryService.handleInvoke(DeliveryService.java:480)
    at com.collaxa.cube.engine.bean.DeliveryBean.handleInvoke(DeliveryBean.java:307)
    at com.collaxa.cube.engine.bean.DeliveryBean_uhics8_ELOImpl.handleInvoke(DeliveryBean_uhics8
    _ELOImpl.java:274)
    at com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessageHandler.handle(Invok
    eInstanceMessageHandler.java:36)
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:64)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
    at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    &lt;2005-02-04 10:24:10,265&gt; &lt;ERROR&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;BaseScheduledWorker::proce
    ss&gt; Failed to handle dispatch message invoke instance message aacf889e30f5e83a:125e791:101ddf7208b:-
    7ffb ... exception Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.mess
    age.invoke.InvokeInstanceMessage"; the exception is: Cannot insert audit trail.
    The process domain was unable to insert the current log entries for the instance "2701" to the audit
    trail table. The exception reported is: The transaction is no longer active - status: 'Marked roll
    back. [Reason=java.lang.NullPointerException]'. No further JDBC access is allowed within this transa
    ction.
    Please check that the machine hosting the datasource is physically connected to the network. Otherw
    ise, check that the datasource connection parameters (user/password) is currently valid.
    sql statement: INSERT INTO audit_trail( cikey, domain_ref, count_id, block, block_csize, block_usiz
    e, log ) VALUES( ?, ?, ?, ?, ?, ?, ? )
    ORABPEL-05002
    Message handle error.
    An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.mess
    age.invoke.InvokeInstanceMessage"; the exception is: Cannot insert audit trail.
    The process domain was unable to insert the current log entries for the instance "2701" to the audit
    trail table. The exception reported is: The transaction is no longer active - status: 'Marked roll
    back. [Reason=java.lang.NullPointerException]'. No further JDBC access is allowed within this transa
    ction.
    Please check that the machine hosting the datasource is physically connected to the network. Otherw
    ise, check that the datasource connection parameters (user/password) is currently valid.
    sql statement: INSERT INTO audit_trail( cikey, domain_ref, count_id, block, block_csize, block_usiz
    e, log ) VALUES( ?, ?, ?, ?, ?, ?, ? )
    at com.collaxa.cube.engine.dispatch.DispatchHelper.handleMessage(DispatchHelper.java:73)
    at com.collaxa.cube.engine.dispatch.BaseScheduledWorker.process(BaseScheduledWorker.java:72)
    at com.collaxa.cube.engine.bean.WorkerBean.onMessage(WorkerBean.java:86)
    at weblogic.ejb20.internal.MDListener.execute(MDListener.java:382)
    at weblogic.ejb20.internal.MDListener.transactionalOnMessage(MDListener.java:316)
    at weblogic.ejb20.internal.MDListener.onMessage(MDListener.java:281)
    at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:2596)
    at weblogic.jms.client.JMSSession.execute(JMSSession.java:2516)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    &lt;2005-02-04 10:24:10,265&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.dispatch&gt; &lt;BaseDispatchSet::acknowled
    ge&gt; Acknowledged message invoke instance message aacf889e30f5e83a:125e791:101ddf7208b:-7ffb
    &lt;2005-02-04 10:24:24,750&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::getConnecti
    on&gt; GOT CONNECTION 1
    &lt;BaseCubeSessionBean::logError&gt; Error while invoking bean "finder": Instance not found in datasource
    The process domain was unable to fetch the instance with key "aacf889e30f5e83a:125e791:101ddf7208b:-
    7ffc" from the datasource.
    Please check that the instance key "aacf889e30f5e83a:125e791:101ddf7208b:-7ffc" refers to a valid in
    stance that has been started and not removed from the process domain.
    &lt;2005-02-04 10:24:24,765&gt; &lt;DEBUG&gt; &lt;default.collaxa.cube.engine.data&gt; &lt;ConnectionFactory::closeConnec
    tion&gt; CLOSE CONNECTION 0
    &lt;&lt;&lt;&lt; Log End &lt;&lt;&lt;&lt;

    hmmm for some reason when you call your EJB and it throws an exception, the JTA transaction is marked as rollbakc so the BPEL EM engine fails to save the instance.
    Could you please provide us some additional pieces of information:
    obversion.bat.
    The exact exception that your EJB throws.
    JTA configuration of your bean
    Have you looked at the BankTransfer demo?
    Edwin

  • Runtime exception in workflow

    We have used the BLOCK task type in our workflow to catch all runtime exceptions. I want the exception details (that gets thrown automatically by the system at runtime) to be sent as part of a notification/mail task type to our administrator.
    1. How do I access these exception details in the mail task type? Is it possible to do this?
    2. For what cases a runtime exception is thrown?
    Is this a valid case - A non existant position specified as receiver of a notification?
    Regards,
    Vikrant

    Dear Vikrant,
    Just try it out....
    Exceptions are triggered using the step u201CProcess Controlu201D. Define a new step u201CProcess Controlu201D in the normal branch. Enter the step name and the outcome name. Select u201CThrow Exceptionu201D in the function. In the event name, select the exception name defined earlier .
    Uncheck u201CStep not in workflow logu201D if you would like to see this step in the workflow log.
    Define a mail step in the exception branch of the block (for testing purpose u2013 to ensure that this exception branch is taken, when the exception is triggered).
    Regards,
    Geet

  • Runtime exceptions from listeners

              When a servlet context listener throws a runtime exception, does the container
              catch it? It seems that
              the container just ignores the exception and tries to go on with life as usual.
              It does not even log the
              exception trace in the server log. Out of desperation, I finally put my entire
              contextInitialized() method
              in a try-block, and created a catch-block for RuntimeException which prints the
              exception stack-trace to
              the console.
              

              "Daniel Steinberg" <[email protected]> wrote:
              >
              >"Chuck Nelson" <[email protected]> wrote:
              >>
              >>Runtime exceptions can occur anywhere in a program and in a typical
              >program
              >>can
              >>be very numerous. The cost of checking for runtime exceptions often
              >exceeds
              >>the
              >>benefit of catching or specifying them. Thus the compiler does not require
              >>that
              >>you catch or specify runtime exceptions, although you can
              >>
              >>Take a look at the following link on a discussion of runtime exceptions
              >>
              >>http://java.sun.com/docs/books/tutorial/essential/exceptions/runtime.html
              >>
              >>Chuck Nelson
              >>Developer Relations Engineer
              >>BEA Technical Support
              >>
              >
              >If a servlet throws a runtime exception, the request fails and
              >exception information is written to the console and to the server
              >log. I would expect similar behavior when a listener throws a
              >runtime exception. A runtime exception generally indicates
              >a precondition violation by the client class (see Bloch,
              >Effective Java, p. 172). So when such an exception ocurrs, the
              >request should die and the developer should be informed of the
              >situation.
              >exception ocurrs, the program should die,
              >
              It seems that I'm not the only one bothered by this behavior
              (which is unspecified in the Servlet 2.3 spec).
              See Bug #4519704 in the JDC Bug Parade.
              

  • How to throw or catch sql exception for executeReader sql adapter

    Wcf sql adapter was created and executeReader was used.
    When an invalid sql statement was constructed and send it to wcf sql adapter, it will hanging there, and no response. No exception was catched even though send chape  was inside a catch block. How can I catch this kind of exception
    or throw this exception ? I need to give client an exception resposne.
    thanks
    Gary

    I used scope with exception handle which has Exception object type: "System.SystemException".
    I guess this type "System.SystemException" can catch any exception, including sql exception. Maybe I am wrong. I got error from window event:
    A message sent to adapter "WCF-Custom" on send port "WcfSendPort_SqlAdapterBinding_DalCore_Custom" with URI "mssql://shig-quad-2k3e1//DataSourceOne?" is suspended.
     Error details: System.Data.SqlClient.SqlException: Incorrect syntax near '='.
    Server stack trace:
       at System.ServiceModel.AsyncResult.End[TAsyncResult](IAsyncResult result)
       at System.ServiceModel.Channels.ServiceChannel.SendAsyncResult.End(SendAsyncResult result)
       at System.ServiceModel.Channels.ServiceChannel.EndCall(String action, Object[] outs, IAsyncResult result)
       at System.ServiceModel.Channels.ServiceChannel.EndRequest(IAsyncResult result)
    Exception rethrown at [0]:
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at System.ServiceModel.Channels.IRequestChannel.EndRequest(IAsyncResult result)
       at Microsoft.BizTalk.Adapter.Wcf.Runtime.WcfClient`2.RequestCallback(IAsyncResult result)
     MessageId:  {B24EF5B8-298A-4D4F-AA98-5E639361A7DB}
     InstanceID: {F8924129-265B-4652-B20E-8D25F8F20A51}
    If  "System.SystemException" can't catch all exception, which type can catch all exception ? I want to catch all exception in this catch block.
    thanks
    Gary

  • Handling Runtime Exceptions after Internationalization

    Hi,
    can any one let me know how to handle runtime exceptions . Like keyMissing exception while trying to retirive a key from .property file . The missing key might be due to a typo as property file is just a txt file . Another type of exception could be not able to find the property file itself. The two options available with resource bundle are the property file and the listResource bundle class.Since property file is just a plain text file it wont be able to catch missing key or missing value error[which could be typing mistake] but the listresourceBundle class wont compile if any of the entities key or the value is missing.. How to deal with this problem?
    Thanks
    Mukul

    Hello everyone,
    I added the addition ACCEPTING TRUNCATION to the above statement and the current runtime error has been solved.
    But now a new runtime error came up.'CONNE_IMPORT_WRONG_OBJECT_TYPE'     of exception 'CX_SY_IMPORT_MISMATCH_ERROR'          
    This is because there is a type conflict between the structured objects.
    The defn of CRT is like this
    DATA:  BEGIN OF CRT .
            INCLUDE STRUCTURE PC22Y.  "Cumulated result table (USA)
    DATA:  END   OF CRT.
    but I dont know where the mismatch is occuring in the data cluster.
    Infact I am very much confused with the data cluster structure.
    How do I resolve this issue?
    Any insights would be appreciated.
    Goldie.

Maybe you are looking for