Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 25111 invoked from network); 9 Nov 2004 21:40:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 9 Nov 2004 21:40:28 -0000 Received: (qmail 26815 invoked by uid 500); 9 Nov 2004 21:40:27 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 26785 invoked by uid 500); 9 Nov 2004 21:40:26 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: List-Id: Reply-To: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 26772 invoked by uid 99); 9 Nov 2004 21:40:26 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Tue, 09 Nov 2004 13:40:24 -0800 Received: (qmail 25115 invoked from network); 9 Nov 2004 21:40:23 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 9 Nov 2004 21:40:23 -0000 Message-ID: <421919258.1100036423491.JavaMail.apache@nagoya> Date: Tue, 9 Nov 2004 13:40:23 -0800 (PST) From: "Dain Sundstrom (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Created: (DERBY-62) TableName not serializable Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N TableName not serializable -------------------------- Key: DERBY-62 URL: http://nagoya.apache.org/jira/browse/DERBY-62 Project: Derby Type: Bug Components: SQL Reporter: Dain Sundstrom I'm not sure how, but sometimes an EmbedSQLException can hold on to a TableName. Since TableName is not serializable we can not ship derby exceptions to remote clients. It is common usage for EJB applications to simply pass exceptions through to remote clients. This is the exception I get when I try to serialize an EmbededSQLException... sorry this is not much help on what is causing EmbededSQLException to hold onto a table name but Java Serialization doesn't throw nice exceptions. 15:34:41,161 FATAL [EjbRequestHandler] Invocation result object is not serializable: org.apache.derby.impl.jdbc.EmbedSQLException java.io.NotSerializableException: org.apache.derby.impl.sql.compile.TableName at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054) at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1224) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1050) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278) at org.openejb.client.EJBResponse.writeExternal(EJBResponse.java:159) at org.openejb.server.ejbd.EjbRequestHandler.processRequest(EjbRequestHandler.java:248) at org.openejb.server.ejbd.EjbDaemon.service(EjbDaemon.java:134) at org.openejb.server.ejbd.EjbServer.service(EjbServer.java:76) at org.openejb.server.ServiceLogger.service(ServiceLogger.java:108) at org.openejb.server.ServiceAccessController.service(ServiceAccessController.java:84) at org.openejb.server.ServicePool$1.run(ServicePool.java:105) at java.lang.Thread.run(Thread.java:552) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira