Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <7471370.1160181021241.JavaMail.root@brutus>
Date: Fri, 6 Oct 2006 17:30:21 -0700 (PDT)
From: "Francois Orsini (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-790) SQLException used by the networked
 interface to Derby is not serializable
In-Reply-To: <1746339400.1136306043669.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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

Francois Orsini updated DERBY-790:
----------------------------------

    Attachment: DERBY-790-v2.stat
                DERBY-790-v2.diff

Knut,

Thanks for the review on this patch.

I've incorporated all the suggestions and increased the amount of test logic as far as comparing the original exception with the serialized one.

As part of the test logic in SqlExceptionTest.java, I'm now also using a batch to execute several batch elements and hence generate a few chained / nested exceptions.

I've tested under 1.3, 1.4, 1.5 & 1.6 Java runtime environments as well as under DerbyNetClient and DerbyNet frameworks as well as well as no framework.

I have tested and called getMessage() several times for _each_ of the serialized exceptions generated from the BatchUpdateException and I'm not getting the behavior you described - I get the exact same message than the original exception with no added string. The comparison of both the original and the serialized exceptions is thoroughly tested in BaseJDBCTestCase.java:assertSQLExceptionEquals() and that includes any chained exceptions.

Hence, I'm not sure how you got into the case you described and I would appreciate if you could post the logic for the test you ran as well as your java and platform environment.

In the meantime, I have attached the new changes.

Thanks,

> 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
>
>
> 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