db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Francois Orsini (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-790) SQLException used by the networked interface to Derby is not serializable
Date Thu, 14 Sep 2006 14:49:24 GMT
    [ http://issues.apache.org/jira/browse/DERBY-790?page=comments#action_12434700 ] 
Francois Orsini commented on DERBY-790:

  > Did your re-verification show any problems? 

I had expanded the current SqlExceptionTest.java but realized the added logic was not proper
in order to verify the fix is working. I added a test to SqlExceptionTest.java which is aimed
at running in a true client/server environment and this is what I need to verify to ensure
the fix is tested in a proper manner.

  > Do you think the fix will make it into 10.2?


> 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:
>         Environment: Windows XP; WebLogic Server 9.0
>            Reporter: David Cabelus
>         Assigned To: Francois Orsini
>             Fix For:
> 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


View raw message