Return-Path: Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: (qmail 31017 invoked from network); 12 Apr 2007 11:30:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Apr 2007 11:30:10 -0000 Received: (qmail 14606 invoked by uid 500); 12 Apr 2007 11:30:14 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 14447 invoked by uid 500); 12 Apr 2007 11:30:13 -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 14436 invoked by uid 99); 12 Apr 2007 11:30:13 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Apr 2007 04:30:13 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.18.1.36] (HELO gmp-ea-fw-1.sun.com) (192.18.1.36) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Apr 2007 04:30:06 -0700 Received: from d1-emea-10.sun.com (d1-emea-10.sun.com [192.18.2.120]) by gmp-ea-fw-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id l3CBTjQQ029064 for ; Thu, 12 Apr 2007 11:29:45 GMT Received: from conversion-daemon.d1-emea-10.sun.com by d1-emea-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) id <0JGD00B01UIM9500@d1-emea-10.sun.com> (original mail from John.Embretsen@Sun.COM) for derby-user@db.apache.org; Thu, 12 Apr 2007 12:29:45 +0100 (BST) Received: from [129.159.112.236] by d1-emea-10.sun.com (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPSA id <0JGD005ZJULFULH3@d1-emea-10.sun.com> for derby-user@db.apache.org; Thu, 12 Apr 2007 12:29:45 +0100 (BST) Date: Thu, 12 Apr 2007 13:28:47 +0200 From: John Embretsen Subject: Re: Problems with Derby 10.2.2.0 In-reply-to: <054F5B1BB94BD943B243C3B39B4F568D174517@victory.Erudine.local> Sender: John.Embretsen@Sun.COM To: Derby Discussion Reply-to: derby-user@db.apache.org Message-id: <461E17EF.7050204@Sun.COM> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <054F5B1BB94BD943B243C3B39B4F568D174517@victory.Erudine.local> User-Agent: Thunderbird 1.5.0.9 (X11/20061229) X-Virus-Checked: Checked by ClamAV on apache.org Andrew Norman wrote: > I have a series of unit tests for our application. Due to issues with > the metadata, I have upgraded to the latest official release (10.2.2.0) > and have started getting the following error message appearing in my tests. > > Caused by: java.lang.SecurityException: sealing violation: package > org.apache.derby.iapi.services.crypto is sealed [snip] > Any ideas on what I should look at. Such sealing violations usually happen when classes in the same Java package are attempted loaded from different sources (jar files). Please double check that you don't have multiple versions of the same jar files in your classpath, especially multiple derby.jar files. -- John