db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-2701) many sealing violation errors in ibm142 and ibm15 jvm test runs of junit tests.
Date Sat, 26 May 2007 12:21:16 GMT

    [ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499308
] 

Mike Matrigali commented on DERBY-2701:
---------------------------------------

My best guess so far at what is going on is that it looks like derbytools.jar has classes
from the "org.apache.derby.iapi.services.io"
package, which seem like they should only be in derby.jar.  In build of  541131 the derbytools.jar
has way fewer classes than in a build
of 541503.  I haven't gotten a chance to narrow down the problem. 

I'll attach listing of the classes in the 2 jar files.

My question is whether this is likely a problem with a code checkin, for instance incorrectly
using a module where it should not be.  Or  
has a correct usage somehow just broke the tools that figure out how to make derbytools.jar?

> many sealing violation errors in ibm142 and ibm15 jvm test runs of junit tests.
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-2701
>                 URL: https://issues.apache.org/jira/browse/DERBY-2701
>             Project: Derby
>          Issue Type: Bug
>          Components: Build tools, Regression Test Failure
>    Affects Versions: 10.3.0.0
>            Reporter: Mike Matrigali
>            Priority: Blocker
>
> The regression runs against the ibm jvms for the past 2 days are seeing 390 errors which
I think the majority are coming from this sealing error.
> I am trying to figure out if this is a build/testing machine problem or a real problem
introduced by thursday night checkins which included:
> 541131 TO 541503:
> I ran in my own client against classes and ibm15 and passed the junit suite.  
> see:
> http://people.apache.org/~fuzzylogic/derby_test_results/main/testlog/ibm142/541503-suites.All_diff.txt
> http://people.apache.org/~fuzzylogic/derby_test_results/main/testlog/ibm15/541503-suites.All_diff.txt
> 1) PrepareStatementTest:embeddedjava.lang.ExceptionInInitializerError
> 	at java.lang.Class.forName1(Native Method)
> 	at java.lang.Class.forName(Class.java:180)
> 	at org.apache.derbyTesting.junit.DriverManagerConnector.loadJDBCDriver(DriverManagerConnector.java:143)
> 	at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:72)
> 	at org.apache.derbyTesting.junit.DriverManagerConnector.openConnection(DriverManagerConnector.java:43)
> 	at org.apache.derbyTesting.junit.TestConfiguration.openDefaultConnection(TestConfiguration.java:957)
> 	at org.apache.derbyTesting.junit.BaseJDBCTestSetup.getConnection(BaseJDBCTestSetup.java:74)
> 	at org.apache.derbyTesting.junit.CleanDatabaseTestSetup.setUp(CleanDatabaseTestSetup.java:65)
> 	at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
> 	at junit.extensions.TestSetup.run(TestSetup.java:23)
> 	at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
> Caused by: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.io:
already loaded
> 	at java.net.URLClassLoader.defineClass(URLClassLoader.java:412)
> 	at java.net.URLClassLoader.access$500(URLClassLoader.java:109)
> 	at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:848)
> 	at java.security.AccessController.doPrivileged1(Native Method)
> 	at java.security.AccessController.doPrivileged(AccessController.java:389)
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:371)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:570)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:442)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:502)
> 	at org.apache.derby.iapi.jdbc.JDBCBoot.boot(Unknown Source)
> 	at org.apache.derby.jdbc.EmbeddedDriver.boot(Unknown Source)
> 	at org.apache.derby.jdbc.EmbeddedDriver.<clinit>(Unknown Source)
> 	... 23 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message