From derby-user-return-8439-apmail-db-derby-user-archive=db.apache.org@db.apache.org Wed Jan 16 06:56:06 2008 Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 48875 invoked from network); 16 Jan 2008 06:56:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Jan 2008 06:56:06 -0000 Received: (qmail 73475 invoked by uid 500); 16 Jan 2008 06:55:54 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 73450 invoked by uid 500); 16 Jan 2008 06:55:54 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 73439 invoked by uid 99); 16 Jan 2008 06:55:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Jan 2008 22:55:54 -0800 X-ASF-Spam-Status: No, hits=0.2 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [196.25.240.74] (HELO ctb-mesg4.saix.net) (196.25.240.74) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2008 06:55:29 +0000 Received: from animal (dsl-244-220-56.telkomadsl.co.za [41.244.220.56]) by ctb-mesg4.saix.net (Postfix) with SMTP id F23B4395F for ; Wed, 16 Jan 2008 08:55:21 +0200 (SAST) Message-ID: <001201c8580c$c4536270$0300000a@animal> From: "Johnny Kewl" To: "Derby Discussion" References: <56a83cd00801141212r136adc5bl49e6672b0ff8c7f4@mail.gmail.com> <003601c856fd$51cb6d20$0300000a@animal> <56a83cd00801150923t499fd9eata1f08e94245d5fc6@mail.gmail.com> Subject: Re: [nbusers] Issues with Derby in customer classloader using Java 6 Date: Wed, 16 Jan 2008 08:55:20 +0200 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Antivirus: avast! (VPS 080101-0, 2008/01/01), Outbound message X-Antivirus-Status: Clean X-Virus-Checked: Checked by ClamAV on apache.org ----- Original Message ----- From: "David Van Couvering" To: "Derby Discussion" ; Sent: Tuesday, January 15, 2008 7:23 PM Subject: Re: [nbusers] Issues with Derby in customer classloader using Java 6 > Thanks for the excellent details. I think what's new in Java 6 is > JDBC4, which includes an entirely new set of subclasses of exceptions, > including SQLTransientException. > > I *suspect* that this is either the new exception code that was needed > to comply with JDBC4 in Derby or the new exception classes in JDBC 4 > itself that are causing issues. > > It's odd that nobody else has hit this yet - a *lot* of people are > running Derby inside J2EE containers on Java 6... Yes exactly... which worries me... maybe throwing my toys around and its my problem ;) I think the sensible thing is to let it lay for a while, I'm doing some heavy stuff so I may be in an area that normal people never want to be, or go. One last thought I had was "wonder what the other dB JDBC versions are"... Ran this code Driver d = DriverManager.getDriver(dbURI); int major = d.getMajorVersion(); int minor = d.getMinorVersion(); For jdbc:h2 it gives Major 1 Minor 0 For jdbc:hsqldb it gives Major 1 Minor 8 I have no idea what that means... The Derby stuff I tried was the very latest on the site, and the very latest J6 download. I have a feeling that others are lagging behind JDBC4 and if so this will come back and haunt me. .... I think the sensible thing is to leave it until is shows its head again... but thanks, v nice