[ http://issues.apache.org/jira/browse/DERBY-790?page=all ]

Knut Anders Hatlen updated DERBY-790:
-------------------------------------

    Attachment: Serialize.java

Thanks, the test changes look great.

The attached repro (Serialize.java) shows the problem with getMessage(). Note 
that I used getCause() to get the actual derby.client.am.SqlException object 
(which is not a java.sql.SQLException), whereas your tests use 
getNextException() which returns a java.sql.SQLException. I ran the repro with 
Sun J2SE 5.0 on Solaris 10 and got the following output:

*** Message from original exception ***

Error for batch element #1: The statement was aborted because it would have 
caused a duplicate key value in a unique or primary key constraint or unique 
index identified by 'SQL061009023735980' defined on 'T'.

*** Message from deserialized exception ***

Error for batch element #1: Error for batch element #1: The statement was 
aborted because it would have caused a duplicate key value in a unique or 
primary key constraint or unique index identified by 'SQL061009023735980' 
defined on 'T'.

> SQLException used by the networked interface to Derby is not serializable
> -------------------------------------------------------------------------
>
>                 Key: DERBY-790
>                 URL: http://issues.apache.org/jira/browse/DERBY-790
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC, Network Client, Network Server
>    Affects Versions: 10.1.1.0
>         Environment: Windows XP; WebLogic Server 9.0
>            Reporter: David Cabelus
>         Assigned To: Francois Orsini
>             Fix For: 10.2.2.0
>
>         Attachments: DERBY-790-v1.diff, DERBY-790-v1.stat, DERBY-790-v2.diff, 
> DERBY-790-v2.stat, Serialize.java
>
>
> When running RMI client tests with Derby,  many tests failed with the 
> following message:
> Caused by: java.rmi.UnmarshalException: Failed to marshal error response: 
> 'org.apache.derby.client.am.SqlException: 'DROP TABLE' cannot be performed on 
> 'SDF014B7' because it does not exist.' because exception ; nested exception 
> is:
>         java.io.NotSerializableException: 
> org.apache.derby.client.net.NetSqlca
>         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:191)
>         at 
> weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:176)
> This issue is a blocking issue for us.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to