Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 84168 invoked from network); 31 May 2007 09:43:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 May 2007 09:43:37 -0000 Received: (qmail 21929 invoked by uid 500); 31 May 2007 09:43:40 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 21893 invoked by uid 500); 31 May 2007 09:43:40 -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: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 21884 invoked by uid 99); 31 May 2007 09:43:40 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 May 2007 02:43:40 -0700 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 May 2007 02:43:36 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id CA27471417D for ; Thu, 31 May 2007 02:43:15 -0700 (PDT) Message-ID: <6214321.1180604595825.JavaMail.jira@brutus> Date: Thu, 31 May 2007 02:43:15 -0700 (PDT) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-2692) Client driver doesn't chain exceptions received from the server In-Reply-To: <23842902.1180035316423.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-2692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500335 ] Knut Anders Hatlen commented on DERBY-2692: ------------------------------------------- I'm not marking the issue as resolved yet, since I think there is one more change that needs to be made. The embedded driver sets the next exception as cause of the exception with initCause() as well as with setNextException(). The client driver only uses setNextException() if the cause is an SQLException. I think the client should do the same as the embedded driver. > Client driver doesn't chain exceptions received from the server > --------------------------------------------------------------- > > Key: DERBY-2692 > URL: https://issues.apache.org/jira/browse/DERBY-2692 > Project: Derby > Issue Type: Bug > Components: JDBC, Network Client > Affects Versions: 10.2.1.6, 10.2.2.0, 10.3.0.0 > Reporter: Knut Anders Hatlen > Assignee: Knut Anders Hatlen > Priority: Minor > Fix For: 10.3.0.0 > > Attachments: d2692.diff, d2692.stat > > > When the client driver receives a chain of exceptions from the server, it generates one exception with the messages from all the server-side exceptions concatenated into one message. No next-exception chain is set up on the client. See the description of DERBY-1440 for an example. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.