DuplicateKeyException is not thrown

I have WL7, SP1.
Trying to create a duplicate entry into the db using an entity bean.Instead of
throwing a DuplicateKeyException, it always throw EJBException.
Is it a bug?

I doubt that is the case.
If the JVM does not find a class (it has nothing to do with jars) it throws the exception.
So if isn't throwing it then it is finding it somewhere.
There are possible reasons for this. For example if the class tree is in the class path (along with the jar.)

Similar Messages

  • Exception is not thrown immediately in Hibernate 3.  Why??

    I am using Hibernate 3.
    If I execute "session.update" and the update is not successful (e.g. value too large), the exception is not thrown immediately.
    For example,
    System.out.println ("pass 1");
    session.update(dataBean) ;
    System.out.println ("pass 2");
    session.getTransaction().commit();
    System.out.println ("pass 3");
    I find if session.update(dataBean) fails, "pass 1" and "pass 2" are printed but "pass 3" is not printed. That meams Hibernate will not throw exception until I execute "commit". Can I force it to throw immediately (i.e. only "pass 1" will be printed) ?
    Thanks in advance.

    O/R mappers such as Hibernate and JDO generally defer communications with the database for as long as possible; for an insert or update transaction that will be until commit().
    This is for several reasons:
    1) general efficiency - a series of update() calls may modify the same attribute of an object multiple times; it's substantially more efficient to update the database just once
    2) database efficiency - when a transaction is in progress, even when nothing is occuring in that transaction, more resources are consumed inthe database than when no transaction is active. For example, if a transaction updates a row and then 10 minutes later commits, then during that interval the database has to keep track of 2 different versions of that row and know which connections see which version of the row.
    3) connection management - DB connections are expensive resources and once a transaction has started updating the DB, it has to tie up a connection for the duration.
    In other words, no matter how long it takes to set up your transaction in Java, a good O/R mapper is not going to begin a database transaction until the last possible moment, which is at commit().
    Can I force it to throw immediatelyYou can call commit() any time you want.
    It sounds like you want the database to do your input data validation for you. That's wrong. You need to validate input (for size, length, whatever) before you attempt to put it in the database.

  • Model - level exceptions not thrown (EJB, 11.1.1.3)

    Hi,
    We noticed that with the latest jdev version (11.1.1.3) exceptions from model layer are not thrown or logged anywhere. Steps to reproduce (HR schema):
    - create a new Application (J2EE template, add ADF Faces and Page Flow to view project)
    - create Entities from tables (Department and Employee)
    - create a session bean
    - add this method
        public void test() {
            Employee emp = null;
            emp.getDepartment();
            System.out.println("test");
        }- expose it through local interface
    - create a data control from the session bean
    - create a new jspx page, and drag&drop the test() method as a button
    - run the project and click the button.
    No exceptions in the console, the only thing I was able to find is this Info in DefaultServer.log
    ####<May 27, 2010 12:02:03 PM CEST> <Info> <EJB> <myMachine> <DefaultServer> <[ACTIVE] ExecuteThread: '8' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0004EFF816A89E472B1E> <583c10bfdbd326ba:-226d29eb:128d928460d:-7ffd-00000000000000a0> <1274954523439> <BEA-010227> <EJB Exception occurred during invocation from home or business: [email protected]1 threw exception: java.lang.NullPointerException> This is a MAJOR issue, it makes development practically impossible. If there isn't any workaround, we are going back to 11.1.1.2 until next release.
    I can send a test case if anyone is interested.
    Pedja

    We have identified the problem, but right now the fix is planned for a later release.
    If this is an urgent/important problem for you, I would suggest that you open a service request with Oracle support and see if you can get a patch for this, or provide a higher priority for this issue.

  • Exceptions from nested includes not thrown to errorPage

    In our application a central dispatcher servlet includes JSPs.
              These JSPs include other JSPs. When an Exception is thrown from one of these
              pages it is not thrown, even when the error page is indicated in the
              included JSP with the page directive and the Exception is explicitly thrown
              from a catch block.
              I apprciate any thoughts.
              Thanks.
              -mc
              

    can u send the code snippet?
    "Abhishek" <[email protected]> wrote in message
    news:[email protected]..
    Hi
    I am having a stateless session bean(SLBean) which uses a singleton
    class(Single1). Both the SLBean and the Single1 are in the same jar
    file. Single1 contains a static method called getInstance() which
    returns the instance of the Single1(if not already existing).
    The probelm is that when I try to do the "Single1.getInstance()" from
    the stateless bean, then some exception( java.rmi.RemoteException:
    EJBException: ;nested Exception is: Java.lang.NullPointerException) is
    thrown.and getInstance() method of Single1 class in never invoked.
    What might be the problem? why am I not able to call my singleton
    class from the staless bean.
    Thanks in advance.
    Abhishek

  • DuplicateKeyException not thrown by WL7.0

    Hello,
    When I call a Create on an entity CMP from a Session bean(using the local interface),
    where the ejbCreate insertion violate the unicity primary key constraint, The
    WL container raise a LocalTransactionRollBackException (with a cause attribute
    embedding a DuplicateKeyException).
    This is a very tedious behaviour as the session can't catch the DuplicateKeyException.
    Do you think this is a correct behaviour ? Do you find the same kind of behaviour
    ? Is there some clean known workaround (different from testing the primary key
    existance before creating the bean)
    It's seems to me that this is a very limit interpretation of the spec (which is
    not very precise on the subject and let to much freedom on the subject, I admit)
    Here is what says the ejb 2.0 spec :
    ====================================
    10.5.8.2 DuplicateKeyException
    The DuplicateKeyException is a subclass of CreateException. It may be thrown by
    the
    Container to indicate to the client or local client that the entity object cannot
    be created because an
    entity object with the same key already exists. The unique key causing the violation
    may be the primary
    key, or another key defined in the underlying database.
    Normally, the Container should not mark the transaction for rollback before throwing
    the exception.
    When the client or local client receives a DuplicateKeyException, the client knows
    that the
    entity was not created, and that the transaction has not typically been marked
    for rollback.
    I hate the 2 words in the previous spec section : "may be" and "Normaly", which
    allows to have too much different behaviour from one Container to another. But
    if DuplicateKeyException cannot be directly catch, what would be its interest

    I think this is a bug. I've encountered similar problem using WL7 + Sybase
    12 Server. I was getting some kind of EJB exception, which was wrapping SQL
    exception. Considering that CreateException is the application exception, WL
    behaviour differs from what is required in 18.3.1. WL behaves as if
    CreateException was a system exception.
    Actually, it is not the exception type I am bothered with. What really
    upsets me is that contaner rolls back the transaction and there is no way to
    continue it. This sucks. Maybe I should file a bug 6 months ago?
    Michael J.
    "nicolas frank" <[email protected]> wrote in message
    news:[email protected]...
    >
    Hello,
    When I call a Create on an entity CMP from a Session bean(using the localinterface),
    where the ejbCreate insertion violate the unicity primary key constraint,The
    WL container raise a LocalTransactionRollBackException (with a causeattribute
    embedding a DuplicateKeyException).
    This is a very tedious behaviour as the session can't catch theDuplicateKeyException.
    >
    >
    Do you think this is a correct behaviour ? Do you find the same kind ofbehaviour
    ? Is there some clean known workaround (different from testing the primarykey
    existance before creating the bean)
    It's seems to me that this is a very limit interpretation of the spec(which is
    not very precise on the subject and let to much freedom on the subject, Iadmit)
    Here is what says the ejb 2.0 spec :
    ====================================
    10.5.8.2 DuplicateKeyException
    The DuplicateKeyException is a subclass of CreateException. It may bethrown by
    the
    Container to indicate to the client or local client that the entity objectcannot
    be created because an
    entity object with the same key already exists. The unique key causing theviolation
    may be the primary
    key, or another key defined in the underlying database.
    Normally, the Container should not mark the transaction for rollbackbefore throwing
    the exception.
    When the client or local client receives a DuplicateKeyException, theclient knows
    that the
    entity was not created, and that the transaction has not typically beenmarked
    for rollback.
    I hate the 2 words in the previous spec section : "may be" and "Normaly",which
    allows to have too much different behaviour from one Container to another.But
    if DuplicateKeyException cannot be directly catch, what would be itsinterest

  • Exception logged but not thrown on invocation of webservice (BEA-000905)

    Using webservices.jar that comes with Weblogic SP3 and ant task clientgen to build the client, I got this warning on console:
    <14/Abr/2005 16H00m BST> <Warning> <Net> <BEA-000905> <Could not open connection with host: localhost and port: 7777.>
    Of course, weblogic is right, localhost:7777 is not listening, but the problem is that the application does not know this, since no exception is thrown. I'm catching for a Throwable and I get nothing. This is severe because I'm changing the state of some records in a DB table if the invocation of the webservice is OK, i.e., if no exception is thrown. But there really is a connection exception...
    Can anyone help?

    Just to clarify: the warning is logged when invoking a webservice and the target machine is down. I'm sniffing the communication through localhost:7777 (so this is the target machine for the invocation), and then it redirects the request to the machine where the webservice is hosted.
    I was expecting to catch an exception like IOException or RemoteException, or even a custom exception that I defined in the throws clause of the webservice method.

  • Wait - interrupt  Why Exception not thrown?

    Hello. I expected that calling interrupt() on a waiting thread should result in InterruptedException thrown by wait(). Nevertheless, in the code below no Exception is thown as if there were no interrupt() call. Actually this snippet prints the same output irregardless of whether interrupt() is called.
    public class Runner {
        synchronized public void foo(){
            System.out.println("before wait in foo()");
            try {
                wait();
            } catch (InterruptedException e) {
                System.out.println("InterruptedException");
                e.printStackTrace();
            System.out.println("after wait in foo()");
        synchronized public void bar(){
            System.out.println("before sleep in bar()");
            try {
                Thread.sleep(10000);
            } catch (InterruptedException e) {
                e.printStackTrace();
            System.out.println("after sleep in bar()");
            notify();
            System.out.println("after notify in bar()");
        public static void main(String[] args) {
            final Runner runner = new Runner();
            Thread t1 = new Thread(new Runnable(){
                public void run() {
                    runner.foo();
            Thread t2 = new Thread(new Runnable(){
                public void run() {
                    runner.bar();
            t1.start();
            t2.start();
            try {
                Thread.sleep(5000);
            } catch (InterruptedException e) {
                e.printStackTrace();
            t1.interrupt();
            System.out.println("t1 interrupted");
    }

    Thanks for your response.
    Still the whole thing is not clear to me.
    Why InterruptedException is not deterministic in this
    case?
    Where is the ?non-deterministic? code in this
    example?The fact that t1.start() is written before t2.start() in you code does not guarantee that foo() method will always be called first. Either the bar() method or foo() method can be invoked firstly, because this is how threads work in Java. Try to invert: put t2.start() before t1.start(), and see what happens. Probably the exception will be thrown in this case, but this behaviour is still non deterministic.
    Please pay attention to timing -
    t1.interrupt() is called in about 5 seconds after
    both threads are started, at the time when one thread
    is in sleep(10000) and the other in wait(). I believe
    that above condition may be taken for granted taking
    in account 5 seconds interval between calls.You know that when you invoke the notify() method inside the bar method() you are making the foo() method not waiting anymore, don?t you? Therefore, if foo() method is called firstly, then the InterruptedException probably won?t be thrown. I said "probably" because the behaviour is non deterministic. Time is relative. If your processor is fast, then probably the exception will never be thrown, but you will never be completely sure. Maybe if there are other executions using your processor, then the processor might be slow for your program, and then the InterruptedException might be thrown. If you want to make your program have the same behaviour always, then you have to use semaphore variables, that indicate when exactly one thread is permitted to run.

  • Why is exception not thrown in AseCommand when "Truncation error occurred"?

    In the below SQL, data is written to SOURCE and from there to TARGET.
    The DECIMAL columns in TARGET are deliberately smaller than those in SOURCE (eg a DECIMAL (12, 2) column populated from a DECIMAL (19,11) source).
    When I run this in an Query tool (eg, SqlDbx) I get the messages:
    "Truncation error occurred
    Command has been aborted"
    But when I run this using the .net Client (supplied with the Developer Edition of ASE 16.0) no exception is thrown (the INSERT fails though).  The method is AseCommand.ExecuteNonQuery().
    Is this deliberate? 
    Is this believed to be correct?
    How can I tell that a truncation error has been raised?
    Thanks
    IF OBJECT_ID ('dbo.TARGET') IS NOT NULL
      DROP TABLE dbo.TARGET
    GO
    CREATE TABLE dbo.TARGET
      S_Name_NVARCHAR NVARCHAR (50) null,
        S_RedComponent_DEC_15_6 decimal(15, 6) NULL,
        S_BlueComponent_DEC_12_2 decimal(12, 2) NULL, 
        S_GreenComponent_DEC_18_10 decimal(18, 10) NULL
    GO
    IF OBJECT_ID ('dbo.SOURCE') IS NOT NULL
      DROP TABLE dbo.SOURCE
    GO
    CREATE TABLE dbo.SOURCE
      Name_NVARCHAR      NVARCHAR (2000) NULL,
      RedComponent_DEC   DECIMAL (19,11) NULL,
      GreenComponent_DEC DECIMAL (19,11) NULL,
      BlueComponent_DEC  DECIMAL (19,11) NULL
    GO
    INSERT INTO dbo.SOURCE (Name_NVARCHAR, RedComponent_DEC, GreenComponent_DEC, BlueComponent_DEC)
    VALUES ('Beige', 272.195, 272.195, 244.42)
    GO
    INSERT INTO dbo.SOURCE (Name_NVARCHAR, RedComponent_DEC, GreenComponent_DEC, BlueComponent_DEC)
    VALUES ('Bisque', 283.305, 253.308, 217.756)
    GO
    INSERT INTO dbo.SOURCE (Name_NVARCHAR, RedComponent_DEC, GreenComponent_DEC, BlueComponent_DEC)
    VALUES ('Black', 0, 0, 0)
    GO
    INSERT INTO dbo.SOURCE (Name_NVARCHAR, RedComponent_DEC, GreenComponent_DEC, BlueComponent_DEC)
    VALUES ('BlanchedAlmond', 283.305, 261.085, 227.755)
    GO
    --Is there data to migrate?
    SELECT LEFT( S.Name_NVARCHAR,8000),S.GreenComponent_DEC,S.GreenComponent_DEC,S.GreenComponent_DEC
    FROM (
    SELECT * FROM SOURCE
    ) S
    --Yes.migrate away!
    --Next line gives a truncation error occurred in Sybase (gives a truncation error occurred in a query tool
    --but fails silently in AseCommand.ExecuteNonQuery).
    INSERT dbo.TARGET (S_Name_NVARCHAR,S_RedComponent_DEC_15_6,S_BlueComponent_DEC_12_2,S_GreenComponent_DEC_18_10)
    SELECT LEFT( S.Name_NVARCHAR,8000),S.GreenComponent_DEC,S.GreenComponent_DEC,S.GreenComponent_DEC
    FROM (
    SELECT * FROM SOURCE
    ) S
    select * from dbo.TARGET

    Hi Dave,
    I am consulting internally on this. To my understanding, this behavior is based on the ASE severity level, as returned in the TDS_EED token. AseExceptions are thrown when severity level is 11 or higher.
    Our docs are not explanatory in this regard.  Once I get clarification we will provide something in the form of wiki or KBA or doc bug to further explain the detail.  Apologize for the delay and problems this caused. I guess since the command is aborted by ASE, therefore no insertion occurs, even though ASE indicates truncation occurs prior - makes this confusing.
    The message severity, etc is controlled by ASE and the client is just following suit according to the TDS spec. Its just lacking in the client docs. This can be remedied.
    ASE does provide the option to allow truncation and not abort.  It's a set command:
    Enter a query:
    1 > set arithabort numeric_truncation off
    Enter a query:
    1 > INSERT dbo.TARGET (S_Name_NVARCHAR,S_RedComponent_DEC_15_6,S_BlueComponent_DEC_12_2,S_GreenComponent_DEC_18_10) SELECT LEFT( S.Name_NVARCHAR,8000),S.GreenComponent_DEC,S.GreenComponent_DEC,S.GreenComponent_DEC FROM (SELECT * FROM SOURCE
    ) S
    4 rows Affected.
    Notice though ASE does NOT send truncation message. This is when it is well known and accepted to insert and truncate the numeric data.
    Cheers,
    -Paul

  • Exception not thrown on Key Exists

    using c# api:
    I have a Btree DB configured with two secondary DB's and a custom comparer, I have initialized the DB with 'DuplicatesPolicy.NONE'. To my understanding this should cause an exception to be raised if I try to enter a duplicate. On Put(), I get no such exception.
    Why? Am I supposed to throw this from comparer? (Actually tried this but it looks like it leaves cursor in undefined state). How Do I get the KeyExists Exception to be raised when a key exists???
    To my understadning I cannot use PutNoDuplicate() as a primary with secondaries cannot have duplicates configured, and you can only use PutNoDuplicate if there is a sorted duplicate policy...
    Any suggestions?

    Hi,
    The documentation could be a little misleading here. If you specify DuplicatesPolicy.NONE for a database, then duplicates will not be allowed in the database, and when trying to put a key/data pair in the database when the key already exist will fail:
    "Insertion when the key of the key/data pair being inserted already exists in the database will fail. "
    Failing here means that there will be no duplicate created, without any exception being thrown as the default behavior is to "Store the key/data pair in the database, replacing any previously existing key if duplicates are disallowed"; see the Database.Put() methods (BTreeDatabase extends from / is a sub-class of Database).
    You should use the PutNoOverwrite method. When the key that your are trying to insert already exists in the database, you will get a KeyExistException exception.
    Regards,
    Andrei

  • Memory accessViolation NOT thrown, when expected

    Hi,
      I have a program that is an image processor. It takes an image as input, does some number crunching exits normally.
    On one image, I noticed that, while I loop over each pixel in the image, I end up in an index that is beyond the image size.
    I would expect a "Access Violation" to be thrown here. But that does not happen.
    Any idea why ?
    I could run this image in a loop with other images or individually, but it never throws an exception.  I know how to fix the problem which would be a boundary condition in my program but I thought there would be some kind of a lock on memory that is
    beyond the scope of a variable.
    thanks,
    MulanSting

    On 7/22/2014 8:11 AM, MulanSting wrote:
    On one image, I noticed that, while I loop over each pixel in the image, I end up in an index that is beyond the image size.
    I would expect a "Access Violation" to be thrown here. But that does not happen.
    Any idea why ?
    C++ doesn't perform strict bounds checking. Accessing an array out of bounds exhibits undefined behavior. "Continues to work but reads random garbage that just happens to be sitting in memory past the end of the array" is one possible manifestation
    of undefined behavior; "crashes with access violation" is another.
    I thought there would be some kind of a lock on memory that is beyond
    the scope of a variable.
    What evidence led you to this conclusion?
    Igor Tandetnik

  • Exceptions not thrown on interrupted SocketChannel.write()

    I just noticed a behaviour of java.nio.channels.SocketChannel.write() that makes me wonder. If write() blocks(), and the channel is closed during this blocking by another thread, AsynchronousCloseException should be thrown.
    However, in most cases this does not happen in my little test app. If any part of the data passed to write() has already been written to TCP before the socket was closed, write() returns without exception.
    Similar behaviour is observed with intterupting. If the thread blocked in write() is interrupted by another thread, it returns immediately and has the interrupted Flag set, but in most cases no Exception is thrown.
    ClosedByInterruptException is only thrown if not any part of the data passed to write() has been passed to TCP.
    Is this a bug or a feature ?

    Yes, i'm pretty sure that it blocks. In my test, the server just accepts the connection and then goes to sleep for a looooong time. The client just connects, and sends 10Meg of fata in one write() call. If i do not interrupt the client, it blocks as long as the server sleeps. In this case, this is the client's stack while blocking:
    Thread [main] (Suspended)     
         FileDispatcher.write0(FileDescriptor, long, int) line: not available [native method]     
         SocketDispatcher.write(FileDescriptor, long, int) line: 29     
         IOUtil.writeFromNativeBuffer(FileDescriptor, ByteBuffer, long, NativeDispatcher, Object) line: 104     
         IOUtil.write(FileDescriptor, ByteBuffer, long, NativeDispatcher, Object) line: 75     
         SocketChannelImpl.write(ByteBuffer) line: 334     
         Channels.write(WritableByteChannel, ByteBuffer) line: 60     
         Channels.access$000(WritableByteChannel, ByteBuffer) line: 47     
         Channels$1.write(byte[], int, int) line: 134     
         Channels$1(OutputStream).write(byte[]) line: 58     
         SocketClient.main(String[]) line: 75     If i start another thread before calling write(), that closes the socket after 3 seconds, the following happens: The call of IOUtil.write() returns ( with a value n that i cannot see in the debugger ), This value n is tested inside SocketChannelImpl.write() via (n > 0 || (n == IOStatus.UNAVAILABLE), what return true. For that reason, AbstractInterruptibleChannel.end(boolean), does not throw an exception.
    Once the server wakes up later, it is able to read about 200K from the socket...
    I tried this on a linux system (kernel 2.6.17, glibc 2.4) with jdk 1.6.0_03. I'm now gonna try it under windows, hold on..
    Of course, if anybody is interested, i'll post the test proggy...

  • Exception in ADEP Workbench 10.0 service not thrown to the dotnet application.

    Our dotnet application is consuming a service that workbench is exposing. The service creates a pdf and also issues a print command to the printer. Exceptions are handled as part of the workbench activity.
    However, the exceptions are not bubbled up to the dotnet layer. Oftentimes the print doesn't work, but the dotnet process continues as if everything went well.
    Is there a way for the exception to be thrown up to the dotnet layer?

    I am getting also that kind of exception when using the upgrade assistant to upgrade from 10.3.6 to 12.1.1.

  • Connect/Socket Timedout Exception is not thrown

    Hi,
    I am getting the following problem very often. when I tried to connect to some URLs I am not able to connect those URLs and they didnot thrown any exceptions also but the process will be running until we kill explictly. here is my code
    URL url = null;
                   String redirectUrl=null;
                   HttpURLConnection.setFollowRedirects(true);
                   URLConnection connection=null;
                   HttpURLConnection httpConnection=null;
                   String urlString = inpuUrl;
                   try {
                        url = new URL(urlString);
                        connection = url.openConnection();
                        connection.setConnectTimeout(30000);
                        if (connection instanceof HttpURLConnection) {
                             httpConnection = (HttpURLConnection) connection;
                             httpConnection.connect();
                             int response = httpConnection.getResponseCode();
                             url = httpConnection.getURL();
                             redirectUrl= url.getHost();          
                   } catch (UnknownHostException eh) {                    
                        log.error(eh.getMessage(), eh);
                   } catch (ConnectException e) {
                        log.error(e.getMessage(), e);
                   } catch (IOException e) {
                        log.error(e.getMessage(), e);
                   } catch (IllegalArgumentException e) {
                        log.error(e.getMessage(), e);
                   } catch (Exception e) {
                        log.error(e.getMessage(), e);
                   }please help me out how can I comeout from this, I want the redirected url of the input url. if it is not able to establish the connection then it shoud return null but the itis not return any thinn and the process is going to sleep mode
    wating for reply.
    Bhaskar

    O/R mappers such as Hibernate and JDO generally defer communications with the database for as long as possible; for an insert or update transaction that will be until commit().
    This is for several reasons:
    1) general efficiency - a series of update() calls may modify the same attribute of an object multiple times; it's substantially more efficient to update the database just once
    2) database efficiency - when a transaction is in progress, even when nothing is occuring in that transaction, more resources are consumed inthe database than when no transaction is active. For example, if a transaction updates a row and then 10 minutes later commits, then during that interval the database has to keep track of 2 different versions of that row and know which connections see which version of the row.
    3) connection management - DB connections are expensive resources and once a transaction has started updating the DB, it has to tie up a connection for the duration.
    In other words, no matter how long it takes to set up your transaction in Java, a good O/R mapper is not going to begin a database transaction until the last possible moment, which is at commit().
    Can I force it to throw immediatelyYou can call commit() any time you want.
    It sounds like you want the database to do your input data validation for you. That's wrong. You need to validate input (for size, length, whatever) before you attempt to put it in the database.

  • Error on not thrown "catch"

    Why does the Java compiler complain about the presence of a "catch" that the previous "try" does not throw?
    I can think of many valid reasons why I would code such statements like experimenting with code and not knowing which way is the way to go.
    The Java compiler could give a warning if at all but essentially treat it as a "NO-OP" (no operation).
    Instead I have to constantly comment/uncomment up and down my code to satisfy this silly Java compiler requirement.

    Why would you want to have code to handle an exception that will never be thrown?
    Anyway you could always have the method just throw Exception and then you wouldnt have to catch individual subclasses.
    Instead I have to constantly comment/uncomment up >and down my code to satisfy this silly Java compiler >requirementYou seem a bit skeptical of java but you have just begun to learn the language. I think as your understanding of java improves, so will your appreciation for the language itself. But hey, if not, somebody's gotta write assembly code - better you than me!!!

  • BPM - Exception not thrown

    Hi ,
    I created a BPM in which I I have
    Receive Step -> Send Step -> Block Step ->
    Block Processing branch - Receive Step ->Send Step
    Block Dead Line Branch - Dead line of 1 minute and Control step for raising exception
    Block Exception handler branch - Control step for cancelling the process.
    My requirement is that, When I receive the first message and within 1 minute if I DO NOT receive the second message the process should be cancelled(Error in SXMB_MONI).
    Right now the process simply waits for ever for the second message and the process is never Cancelled.
    Any help is greatly appreciated.
    Regards,
    Nazim

    Nazim,
    Try this.
    - Click on the Block Step, in the Properties window give some exception name.
    - Now in the Deadline branch Keep Control Step.
    - Click on the Control Step , choose Action Throw Exception and choose the exception you gave for block step.
    - Remember don't use exception branch, Coz as per your requirement you want to fail the BPM, if you use exception branch then it means again you are catching that. Hence don't use exception branch.
    raj.

Maybe you are looking for

  • Copying and pasting Garageband track data from a project file to another?

    I am recording my music using an iBook and Garage band in the room where I havemy musical instruments and MIDI equipment. Then, using a one Gb Kingston memory stick, I move the files to my brand new 24" Intel iMac in another room. When the files are

  • Adobe Reader 11 will not return to last page read, but version 10 did

    Hi, I have just installed Adobe Reader version 11. When I start reading a pdf, it will not begin on the page where I last left off. I had version 10 and it would begin on the page where I last left off (in the previous session). Is there a way to get

  • How can I download a web page's text only?

    Hello All I have some code (below) which can download the html of a web page and this is usually good enough for me. However, sometimes it would just be easier to work with if I could download just the text only of a given page. And sometimes the tex

  • Can AnyConnect & Cisco IPsec co-exist on client pc?

    Hi- a home user has to connect to one business using AnyConnect and to us using Cisco IPsec client. When installing AnyConnect, it wiped out the IPSec client. Can they co-exist on his pc and function side by side? I'm sure they can't be used simultan

  • Check if uploaded image is CMYK in ActionScript 3.0

    Hey guys, Is there any way to figure this out which user uploaded image in our flex project is RGB or CMYK? Something like using byteArray and check the specific place of CMYK/RGB header on it...