[
https://issues.apache.org/jira/browse/DERBY-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Knut Anders Hatlen updated DERBY-790:
-------------------------------------
Attachment: derby-790-10.2.diff
There was a conflict in SqlExceptionTest so the fix couldn't be merged
automatically, but the conflict was easy to resolve. The attached patch applies
cleanly on 10.2. I'm running derbyall on it now and will commit if there are no
problems.
> SQLException used by the networked interface to Derby is not serializable
> -------------------------------------------------------------------------
>
> Key: DERBY-790
> URL: https://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
> Attachments: derby-790-10.2.diff, DERBY-790-v1.diff,
> DERBY-790-v1.stat, DERBY-790-v2.diff, DERBY-790-v2.stat, DERBY-790-v3.diff,
> DERBY-790-v3.stat, DERBY-790-v5.diff, DERBY-790-v5.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.
-
You can reply to this email to add a comment to the issue online.
