Parameters when a idl exception is thrown

I am trying to assign a value to a parameter passed to a server through corba...that value varies based on whether or not there is an exception...It works fine with no exceptions, and is assigned the correct value on the server side and is received on the client side....when there is an exception, it is assigned the correct value in the catch on the server side, then I rethrow the exception to be caught on the client side, but the parameter is received as null (it's an array) on the client side...Is there any way to assign this parameter in the exception handling on the server side and have it retain it's value in the exception handling on the client side?

I'm having a hard time trying to visualize what your code looks like. Why don't you just include the required value in the exception thrown? (throwing a new exception of course probably with the original one as the 'detail').

Similar Messages

Populating OUT parameters when TOO_MANY_ROWS exception is thrown

When I was trying to write code to test out today's PL/SQL challenge quiz, the behavior appears to depend on the table being queried. I can't figure out what attribute of the table drives the behavior (or if there is a different explanation for the behavior).
The quiz is testing what happens when a procedure does a SELECT INTO an OUT parameter and a TOO_MANY_ROWS exception is thrown. The intent is to show that even though the behavior is technically undefined, what actually happens is that the OUT parameter is populated with the first row that is selected (obviously, you would never write code that depends on this behavior-- this is solely an academic exercise). The demonstration code works as expected
CREATE TABLE plch_emp ( emp_name VARCHAR2(100) );
INSERT INTO plch_emp VALUES ('Jones');
INSERT INTO plch_emp VALUES ('Smith');
COMMIT;
CREATE OR REPLACE PROCEDURE plch_get
(out_name OUT plch_emp.emp_name%TYPE) IS
BEGIN
SELECT emp_name
INTO out_name
FROM plch_emp
ORDER BY emp_name;
EXCEPTION
WHEN OTHERS THEN
    dbms_output.put_line('A:' || out_name);
END;
What will be displayed after executing the following block:
DECLARE
l_name plch_emp.emp_name%TYPE;
BEGIN
plch_get(l_name);
dbms_output.put_line('B:' || l_name);
END;
/and outputs
A:Jones
B:JonesWhen I replicate the logic while hitting the EMP table, the PLCH_EMP table, and the newly created EMP2 table, however, I get different behavior for the EMP and EMP2 tables. The procedure that queries PLCH_EMP works as expected but the OUT parameter is NULL when either EMP or EMP2 are created. Any idea what causes the behavior to differ?
select *
from v$version;
create table emp2
as
select *
from emp;
create or replace procedure p1( p_out out varchar2 )
is
begin
select emp_name
    into p_out
    from plch_emp
   order by emp_name;
exception
when others then
    dbms_output.put_line( 'P1 A:' || p_out );
end;
create or replace procedure p2( p_out out varchar2 )
is
begin
select ename
    into p_out
    from emp
   order by ename;
exception
when others then
    dbms_output.put_line( 'P2 A:' || p_out );
end;
create or replace procedure p3( p_out out varchar2 )
is
begin
select ename
    into p_out
    from emp2
   order by ename;
exception
when others then
    dbms_output.put_line( 'P3 A:' || p_out );
end;
declare
l_ename varchar2(100);
begin
p1( l_ename );
dbms_output.put_line( 'P1 B:' || l_ename );
p2( l_ename );
dbms_output.put_line( 'P2 B:' || l_ename );
p3( l_ename );
dbms_output.put_line( 'P3 B:' || l_ename );
end;
SQL> select *
2    from v$version;
BANNER
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
PL/SQL Release 11.2.0.1.0 - Production
CORE    11.2.0.1.0      Production
TNS for 64-bit Windows: Version 11.2.0.1.0 - Production
NLSRTL Version 11.2.0.1.0 - Production
SQL>
SQL> create table emp2
2 as
3 select *
4    from emp;
Table created.
SQL>
SQL> create or replace procedure p1( p_out out varchar2 )
2 is
3 begin
4    select emp_name
5      into p_out
6      from plch_emp
7     order by emp_name;
8 exception
9    when others then
10      dbms_output.put_line( 'P1 A:' || p_out );
11 end;
12 /
Procedure created.
SQL>
SQL> create or replace procedure p2( p_out out varchar2 )
2 is
3 begin
4    select ename
5      into p_out
6      from emp
7     order by ename;
8 exception
9    when others then
10      dbms_output.put_line( 'P2 A:' || p_out );
11 end;
12 /
Procedure created.
SQL>
SQL> create or replace procedure p3( p_out out varchar2 )
2 is
3 begin
4    select ename
5      into p_out
6      from emp2
7     order by ename;
8 exception
9    when others then
10      dbms_output.put_line( 'P3 A:' || p_out );
11 end;
12 /
Procedure created.
SQL>
SQL> declare
2    l_ename varchar2(100);
3 begin
4    p1( l_ename );
5    dbms_output.put_line( 'P1 B:' || l_ename );
6
7    p2( l_ename );
8    dbms_output.put_line( 'P2 B:' || l_ename );
9
10    p3( l_ename );
11    dbms_output.put_line( 'P3 B:' || l_ename );
12
13 end;
14 /
P1 A:Jones
P1 B:Jones
P2 A:
P2 B:
P3 A:
P3 B:
PL/SQL procedure successfully completed.Justin

Billy Verreynne wrote:
So we can then reasonably assume that the test or environment itself somehow interferes with the results? After all, the very same cursor is executed and the same PL/SQL engine uses that cursor interface.Clearly, there is something in my environment that is wonky. It just bugs me that I can't figure out what that variable is.
Your test was done as a single anonymous PL/SQL block. Which means each proc that was called referenced the same variable/memory - are there perhaps PL/SQL optimisation enabled for the database or session? Or any other settings that could influence the test? Have you tried calling the procedures directly from SQL*Plus using a bind var and not via an anon block and a local var in that block?I have. And the results were the same
SQL> var ename varchar2(100);
SQL> exec p1( :ename );
P1 A:Jones
PL/SQL procedure successfully completed.
SQL> exec p2( :ename );
P2 A:
PL/SQL procedure successfully completed.
SQL> exec p3( :ename );
P3 A:
PL/SQL procedure successfully completed.
As a sanity test - what happens when proc P3 for example is changed to a catersian join/union of emp2 and plch_emp? Do the test results change? Or you can change it as follows:
SQL> ed
Wrote file afiedt.buf
1 create or replace procedure p5( p_out out varchar2 )
2 is
3 begin
4    --// force a value into p_out using a successful fetch
5    select emp_name
6      into p_out
7      from plch_emp
8     where rownum = 1;
9    --// force an error and determine if p_out was overwritten
10    select ename
11      into p_out
12      from emp2
13     order by ename;
14 exception
15    when others then
16      dbms_output.put_line( 'P5:' || p_out );
17* end;
18 /
Procedure created.
SQL> exec p5( :ename );
P5:Jones
PL/SQL procedure successfully completed.
Of course, you can also put this one down to using an operating system like Windows as a poor database server and not as a magnificent client gaming platform... Well, sure. But you can probably only play World of Warcraft so long before you need to write some PL/SQL.
Justin

How to fail messsages when timeout exception is thrown in BPM?

Hi
In my BPM, if the time out exception is thrown in BPM, in SXMB_MONI, all the inbound messages' staus is 'processed sucessfully' ? How can I make the message fail? With a red flag or anything indicating exception?
In my design I used deadline branch to throw time out exception.And in the exception branch I used control step to cancel the process.

Hi,
In my design I used deadline branch to throw time out exception.And in the exception branch I used control step to cancel the process
If this is what you have designed then increasing the timeout using the above mentioned blogs doesn't seem to be logical:) (BPM will throw the error when the deadline is meet....can't understand how by increasing timeout will help you)....instead of increasing the timeout you can increase the time limit mentioned in the deadline branch itself to ensure that your message will be processed in that particular time limit.
Since you have reached the timeout it means that desired message processing has failed so better you raise an alert instead of going for a increase in timeout....increasing timeout decreases performance...
Regards,
Abhishek.

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 is thrown when creating bean

          Hi, I have some questions about transaction.
          In my case, i call a stateful session bean through the stateless session bean.
          When the bean is created, following exception is thrown
          "javax.transaction.TransactionRolledbackException: Current server is the coordinator
          and transaction is not found. It was probably rolled back and forgotten already."
          The transaction attribute of the stateless session bean is "Required" and the
          one of stateful session bean is "NotSupported".
          I dont know what is happening, would anyone help me please.
          Thanks


Try asking this in the interest.ejb group.
          Thanks.
          "Leo" <[email protected]> wrote in message news:3f7b7c21$[email protected]..
          >
          > Hi, I have some questions about transaction.
          > In my case, i call a stateful session bean through the stateless session bean.
          > When the bean is created, following exception is thrown
          >
          > "javax.transaction.TransactionRolledbackException: Current server is the coordinator
          > and transaction is not found. It was probably rolled back and forgotten already."
          >
          > The transaction attribute of the stateless session bean is "Required" and the
          > one of stateful session bean is "NotSupported".
          >
          > I dont know what is happening, would anyone help me please.
          >
          > Thanks
          >
          >

No exception is thrown when my server socket dies

I have a server application running on sunOS 5.7.
To this I have both Windows and SunOS clients connected via TCP/IP. (Server built with jdk 1.2.2 and client with 1.3.0)
If the Server socket dies an exception is thrown in the windows clients but not in the sunOS client.
I need the exception to be thrown in the sunOS as well.
Is there anybody who knows how to get this done?
Thanks in advance.
/Henrik

You could poll the connection to see if its there.
If you want the client to register the event then have your client create a sort of listener of your own when it connects. By 'sort of listener' I mean extend the thread class and have it check the connection is not null every n seconds. If it is null then raise the exception yourself.
Would this do it?
Rob.

Detecting when exception was thrown using custom class loader

Hello all,
I would like to implement the solution described here - http://stackoverflow.com/questions/75218/how-can-i-detect-when-an-exceptions-been-thrown-globally-in-java - that uses custom class loader in order to detect when an Exeption thrown somewhere in the JVM hosting my app, please note that exceptions might be thrown from 3rd party jars the app is using. So, thanks to help I got from another post, I've managed to code the custom class loader. My question is how can the class loader wrap the original exception, as the methods in ClassLoader deals with classes, not instances. So where should I set the original exception?
Thanks!
Edited by: user9355666 on Sep 28, 2010 10:48 PM

user9355666 wrote:
I think I'm missing something fundumental, forgive me for being slow...
This is what I did so far. For the exception wrapper I made a simple class extens Exception that recieve Exception in its ctor and store it. I also subclassed ClassLoader and override its loadClass(). I've registered it as the system classloader. My thinking was to check in that point that if the requested class is instance of Exception and if yes, returning my wrapper class wrapping this exception. But, since loadClass() return class, how can I set in the wrapper the original exception?
In addition, let's say 2 different places in the code throws NPE, to my understanding the classloader will load NPE only once, so how throwing the NPE in the second time can be detected?you are missing a key point. you should creating a custom implementation of the NPE class which hooks into your detection code in its constructor. from that point forward, anytime any NPE (which is your custom class) is constructed, you can detect it.

How can the eclipse debugger break in the code when an exception is thrown

Is there a way in eclipse to break into the bebugger when an exception is thrown in debug mode like Visual Studio 2003 or 2005?
Thanks

For 3.x, select "Add Java Exception Breakpoint" from the "Run" menu.
Check "Caught" to break even if your code handles the exception, "Uncaught" to break when your code doesn't handle the exception.

Exception is thrown when Memebr roles is used in XML JAZN

Hi,
I am trying to use the Member roles feature in the JAZN xml file. However, Once you run the application below exception is thrown.
08/08/31 00:33:18 oracle.security.jazn.JAZNObjectNotFoundException
08/08/31 00:33:18      at oracle.security.jazn.spi.xml.XMLRealmRole.init(XMLRealmRole.java:310)
08/08/31 00:33:18      at oracle.security.jazn.spi.xml.XMLRoleManager.init(XMLRoleManager.java:186)
08/08/31 00:33:18      at oracle.security.jazn.spi.xml.XMLRealm.init(XMLRealm.java:200)
08/08/31 00:33:18      at oracle.security.jazn.spi.xml.XMLRealmManager.init(XMLRealmManager.java:167)
08/08/31 00:33:18      at oracle.security.jazn.spi.xml.XMLJAZNProvider.parseDataFile(XMLJAZNProvider.java:403)
08/08/31 00:33:18      at oracle.security.jazn.spi.xml.XMLJAZNProvider.getRealmManager(XMLJAZNProvider.java:480)
08/08/31 00:33:18      at oracle.security.jazn.spi.GenericProvider.getRealmManager(GenericProvider.java:143)
08/08/31 00:33:18      at oracle.security.jazn.JAZNConfig.getRealmManager(JAZNConfig.java:1014)
08/08/31 00:33:18      at oracle.security.jazn.oc4j.JAZNUserManager.getUMType(JAZNUserManager.java:5156)
08/08/31 00:33:18      at oracle.security.jazn.oc4j.JAZNUserManager.getUM(JAZNUserManager.java:5208)
08/08/31 00:33:18      at oracle.security.jazn.oc4j.JAZNUserManager.<init>(JAZNUserManager.java:5245)
08/08/31 00:33:18      at com.evermind.server.deployment.UserManagerConfig$JAZN.construct(UserManagerConfig.java:629)
08/08/31 00:33:18      at com.evermind.server.deployment.UserManagerConfig.delegatee(UserManagerConfig.java:289)
08/08/31 00:33:18      at com.evermind.security.IndirectUserManager.getAdminUser(IndirectUserManager.java:126)
08/08/31 00:33:18      at com.evermind.security.IndirectUserManager.getAdminUser(IndirectUserManager.java:126)
08/08/31 00:33:18      at com.evermind.server.XMLApplicationServerConfig.setPassword(XMLApplicationServerConfig.java:3011)
08/08/31 00:33:18      at com.evermind.server.ApplicationServerLauncher.run(ApplicationServerLauncher.java:95)
08/08/31 00:33:18      at java.lang.Thread.run(Thread.java:595)
Can anybody help me solving this problem?!

Younis2,
That was the important piece of information you needed to provide ;) I get the same exception if I try to do nested roles, but it doesn't prevent my application from starting - looks like it may be a bug - suggest you post a new thread with the word BUG in the title and give a really simple test case. I was able to reproduce quite simply by using tools->embedded oc4j preferences, and then editing the jazn configuration there to nest one role inside of another.
John

Memory leak when exceptions are thrown?

Hello,
I'm doing a simple database connect with the JDBC Oracle 8.1.6 oci8 drivers on Solaris. It seems whenever I try to repeatedly connect to a database, and an exception is thrown, such as database not found, or wrong password, the program size grows and grows until it runs out of memory. I've narrowed it down to being the getConnection operation as the casue of this memory leak.
Now, if I repeatedly connect successfully, there is no problem, it will run all day, but if there are exceptions thrown, memory leaks. Has anyone else encountered this?
I'll paste a sample program below which shows the problem. Maybe someone can help???
import java.sql.*;
import java.util.*;
import java.io.*;
public class connect extends Thread {
private oracle.jdbc.driver.OracleDriver oDriver = new oracle.jdbc.driver.OracleDriver();
private Connection connection;
* Open a connection to the database
private void connectToDB() {
try {
connection = DriverManager.getConnection ("jdbc:oracle:oci8:@test", "test", "test");
connection.close();
} catch (SQLException e) {
e.printStackTrace();
System.out.println("couldn't connect");
public void run() {
try {
DriverManager.registerDriver(oDriver);
} catch (SQLException e) {}
while(true) {
try {
sleep(1000);
connectToDB();
} catch (InterruptedException ie) {}
public static void main(String[] args) {
connect conn = new connect();
conn.start();
null

Try this:
private void connectToDB() {
try {
connection = DriverManager.getConnection ("jdbc:oracle:oci8:@test", "test", "test");
} catch (SQLException e) {
e.printStackTrace();
System.out.println("couldn't connect");
finally {
connection.close();
null

JUnit - How to assert exception is thrown?

If I use JUnit how do I assert an exception is thrown when I pass invalid parameters to a method I am testing? For example if I pass a username to a method that I know will cause the method to throw an InvalidUsernameException how do I assert this?

public void testBadParameter() {
try {
    objectUnderTest.myMethod(badParameter);
    fail("Foo!");
} catch (ExcpectedException e) {
    //ok
}

NO EXCEPTION IS THROWN FROM THE PERSIST

We are using Glassfish and MySQL. When we do a persist with a bad object/query, internal DB errors are NOT being reported back to the caller in any way, but Glassfish knows that the error occurred. Here is a schematic of the situation:
     Glassfish starts a CMP transaction and calls our bean
          Inside the bean we have code like this:
               obj = (a new object that will cause a DB error when persisted)
               try {
                    entityManager.persist(obj)
               } catch (Throwable t) {
                    report to the user that the throwable happened
          bean returns
     Glassfish manages CMP transaction
What we see is the following:
     - The persist has an internal failure and generates error messages in the Glassfish system.log file.
     - NO EXCEPTION IS THROWN FROM THE PERSIST, so the application code thinks that the persist completed correctly
     - At the end of the bean operation, Glassfish (correctly) rolls back the transaction.
At the user level the result is that the request succeeds but nothing is put into the Database!
We are not asking about the cause of the DB error. From reading the system log we know what happened and can fix it. Our problem is that problems in our field-deployed systems cannot be detected by the application code so failures cannot be reported to the user.
The critical question is:
     Is there a way for the application code in the bean to see that an error occurred?
By the way, we also have a secondary question: Why is the erroneous persist tried 6 times before deciding it won't work? Is there an option somewhere that says to try 6 times?
The Exception as reported in the system log (only one copy of it) is included below.
[#|2008-10-22T08:32:25.992-0400|WARNING|sun-appserver9.1|oracle.toplink.essentials.session.file:/opt/localVendors/glassfish/tems-glassfish-v1/domains/domain1/applications/j2ee-apps/im-app/im-ejb_jar/-local|_ThreadID=138;_ThreadName=p: thread-pool-1; w: 156;_RequestID=509e7043-21bb-410c-b795-19e9953afeec;|
Local Exception Stack:
Exception [TOPLINK-4002] (Oracle TopLink Essentials - 2.0.1 (Build b04-fcs (04/11/2008))): oracle.toplink.essentials.exceptions.DatabaseException
Internal Exception: com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException: Column 'STATIONCODE' cannot be null
Error Code: 1048
Call: INSERT INTO <exact operation and table contents elided from this trace file>
     at oracle.toplink.essentials.exceptions.DatabaseException.sqlException(DatabaseException.java:311)
     at oracle.toplink.essentials.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:654)
     at oracle.toplink.essentials.internal.databaseaccess.DatabaseAccessor.executeNoSelect(DatabaseAccessor.java:703)
     at oracle.toplink.essentials.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:492)
     at oracle.toplink.essentials.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:452)
     at oracle.toplink.essentials.internal.sessions.AbstractSession.executeCall(AbstractSession.java:690)
     at oracle.toplink.essentials.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:228)
     at oracle.toplink.essentials.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:214)
     at oracle.toplink.essentials.internal.queryframework.DatasourceCallQueryMechanism.insertObject(DatasourceCallQueryMechanism.java:346)
     at oracle.toplink.essentials.internal.queryframework.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:191)
     at oracle.toplink.essentials.internal.queryframework.StatementQueryMechanism.insertObject(StatementQueryMechanism.java:205)
     at oracle.toplink.essentials.internal.queryframework.DatabaseQueryMechanism.insertObjectForWrite(DatabaseQueryMechanism.java:564)
     at oracle.toplink.essentials.queryframework.InsertObjectQuery.executeCommit(InsertObjectQuery.java:89)
     at oracle.toplink.essentials.internal.queryframework.DatabaseQueryMechanism.performUserDefinedWrite(DatabaseQueryMechanism.java:750)
     at oracle.toplink.essentials.internal.queryframework.DatabaseQueryMechanism.performUserDefinedInsert(DatabaseQueryMechanism.java:714)
     at oracle.toplink.essentials.internal.queryframework.DatabaseQueryMechanism.insertObjectForWriteWithChangeSet(DatabaseQueryMechanism.java:602)
     at oracle.toplink.essentials.queryframework.WriteObjectQuery.executeCommitWithChangeSet(WriteObjectQuery.java:162)
     at oracle.toplink.essentials.internal.queryframework.DatabaseQueryMechanism.executeWriteWithChangeSet(DatabaseQueryMechanism.java:390)
     at oracle.toplink.essentials.queryframework.WriteObjectQuery.executeDatabaseQuery(WriteObjectQuery.java:109)
     at oracle.toplink.essentials.queryframework.DatabaseQuery.execute(DatabaseQuery.java:628)
     at oracle.toplink.essentials.queryframework.DatabaseQuery.executeInUnitOfWork(DatabaseQuery.java:555)
     at oracle.toplink.essentials.queryframework.ObjectLevelModifyQuery.executeInUnitOfWorkObjectLevelModifyQuery(ObjectLevelModifyQuery.java:138)
     at oracle.toplink.essentials.queryframework.ObjectLevelModifyQuery.executeInUnitOfWork(ObjectLevelModifyQuery.java:110)
     at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.internalExecuteQuery(UnitOfWorkImpl.java:2233)
     at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:952)
     at oracle.toplink.essentials.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:909)
     at oracle.toplink.essentials.internal.sessions.CommitManager.commitNewObjectsForClassWithChangeSet(CommitManager.java:269)
     at oracle.toplink.essentials.internal.sessions.CommitManager.commitAllObjectsWithChangeSet(CommitManager.java:190)
     at oracle.toplink.essentials.internal.sessions.AbstractSession.writeAllObjectsWithChangeSet(AbstractSession.java:2657)
     at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.commitToDatabase(UnitOfWorkImpl.java:1044)
     at oracle.toplink.essentials.internal.ejb.cmp3.base.RepeatableWriteUnitOfWork.commitToDatabase(RepeatableWriteUnitOfWork.java:403)
     at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.commitToDatabaseWithChangeSet(UnitOfWorkImpl.java:1126)
     at oracle.toplink.essentials.internal.sessions.UnitOfWorkImpl.issueSQLbeforeCompletion(UnitOfWorkImpl.java:2443)
     at oracle.toplink.essentials.internal.ejb.cmp3.base.RepeatableWriteUnitOfWork.issueSQLbeforeCompletion(RepeatableWriteUnitOfWork.java:202)
     at oracle.toplink.essentials.transaction.AbstractSynchronizationListener.beforeCompletion(AbstractSynchronizationListener.java:131)
     at oracle.toplink.essentials.transaction.JTASynchronizationListener.beforeCompletion(JTASynchronizationListener.java:91)
     at com.sun.jts.jta.SynchronizationImpl.before_completion(SynchronizationImpl.java:99)
     at com.sun.jts.CosTransactions.RegisteredSyncs.distributeBefore(RegisteredSyncs.java:158)
     at com.sun.jts.CosTransactions.TopCoordinator.beforeCompletion(TopCoordinator.java:2548)
     at com.sun.jts.CosTransactions.CoordinatorTerm.commit(CoordinatorTerm.java:278)
     at com.sun.jts.CosTransactions.TerminatorImpl.commit(TerminatorImpl.java:249)
     at com.sun.jts.CosTransactions.CurrentImpl.commit(CurrentImpl.java:623)
     at com.sun.jts.jta.TransactionManagerImpl.commit(TransactionManagerImpl.java:309)
     at com.sun.enterprise.distributedtx.J2EETransactionManagerImpl.commit(J2EETransactionManagerImpl.java:1030)
     at com.sun.enterprise.distributedtx.J2EETransactionManagerOpt.commit(J2EETransactionManagerOpt.java:397)
     at com.sun.ejb.containers.BaseContainer.completeNewTx(BaseContainer.java:3792)
     at com.sun.ejb.containers.BaseContainer.postInvokeTx(BaseContainer.java:3571)
     at com.sun.ejb.containers.MessageBeanContainer.afterMessageDeliveryInternal(MessageBeanContainer.java:1226)
     at com.sun.ejb.containers.MessageBeanContainer.afterMessageDelivery(MessageBeanContainer.java:1197)
     at com.sun.ejb.containers.MessageBeanListenerImpl.afterMessageDelivery(MessageBeanListenerImpl.java:79)
     at com.sun.enterprise.connectors.inflow.MessageEndpointInvocationHandler.invoke(MessageEndpointInvocationHandler.java:139)
     at $Proxy364.afterDelivery(Unknown Source)
     at com.sun.messaging.jms.ra.OnMessageRunner.run(OnMessageRunner.java:324)
     at com.sun.enterprise.connectors.work.OneWork.doWork(OneWork.java:76)
     at com.sun.corba.ee.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:555)
Caused by: com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException: Column 'STATIONCODE' cannot be null
     at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:931)
     at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2985)
     at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1631)
     at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723)
     at com.mysql.jdbc.Connection.execSQL(Connection.java:3283)
     at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1332)
     at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1604)
     at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1519)
     at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:1504)
     at com.mysql.jdbc.jdbc2.optional.PreparedStatementWrapper.executeUpdate(PreparedStatementWrapper.java:840)
     at oracle.toplink.essentials.internal.databaseaccess.DatabaseAccessor.executeDirectNoSelect(DatabaseAccessor.java:647)
     ... 53 more
|#]

This is because the persistent context is not synchronized with the database until the commit is being executed.
You might 'force' this by calling entityManager.flush() right after the call to persist(...).
Or you register a transaction synchronizer and check the transaction status on afeterCompletion().
- Roy

Exception is thrown "mydb is not bound"(needs urgent help)

We r three students and our final project is a BPM(Business peocess Management)system.
BPM is actually a workflow system(managing the business processes)and all the rules and constraints are applied from the Rule Management System.
we have started the implementation, and therefore we need some help related to the implementation.
We r using EJB2.0 with JBuilder9, JBoss3.2 as the application server and tomcate as the web server.
problem:
I want to create manual database connection using DataSource,
I am using mysql and database name is mydb.
I have done all the reqiured configration of mysql with Joss and it is working.
After getting the initial context, when i try to lookup the datasource, exception is thrown "mydb is not bound"
Initial context is correct because i have tried entity beans asd it works well.
code is
Hashtable contextValues = new Hashtable();
contextValues.put(Context.PROVIDER_URL, "jnp://loopback:1099");
contextValues.put(Context.INITIAL_CONTEXT_FACTORY,
"org.jnp.interfaces.NamingContextFactory");
Context context = new InitialContext(contextValues);
context.lookup("java://mydb");
Kindly help me if u find time,
regards!

try java:comp/env/jdbc/mydb or java:comp/env/mydb

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

Web Service: Response has null value and no exception is thrown

Hi
I have generated a Web Service Proxy in JDeveloper 11gR1 against a web service.
My problem is that if I try to invoke the web service programmatically the only property on the response object has the null value. I can inspect the response in the Http Analyzer and it seems to understand and display content of the response properly.
I have debugged the service proxy and discovered that the set-method on the property is never called. No exceptions are thrown, so it is very hard to see where to start solving this issue!
Any ideas?

When a webservice provides a response that is not valid according to its wsdl, a webservice proxy in 10g will give useful error messages such as "Missing element 'xxx'."
In 11g the web service proxy simply sets non-valid values to null, quietly accepting the invalid response. Is this the intended behavior?
Is it possible to enter a debug mode, where the webservice response is validated against the wsdl as in 10g?
I appreciate any help on this question.
Thanks!

Parameters when a idl exception is thrown

Similar Messages

Maybe you are looking for