[
https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Matrigali updated DERBY-2701:
----------------------------------
I have not had a chance to do anymore debugging on this issue, but wanted to
summarize some info I learned from myrna about the environment that the ibm
jvm regressions tests are run.
1) recently the class path for running the junit suite was changed to not
include derby.jar, as it should be automatically
brought in as part of other jar's. In the regression tests only this
suite's classpath was changed. The derbyall
classpath was not changed so it explicitly has derby.jar in classpath.
Maybe sealing violation only happens if a duplicate
class is found in a jar that is faulted in, in this manner? I am not sure
exactly when this change went in but I believe it
predated when all these errors started appearing.
2) some other junit suite runs against the same set of jars on linux with
ibm15, with the old classpath are not seeing
sealing violation.
If I get time I may kick off a script which does a jar build for each change
between 541131 and 541503 to figure out what
change triggered the bloat in derbytools.jar. If anyone already has these
jars, let me know.
If anyone knows what the classpath looks like for the sun regression test
suites do let the list know.
> 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
> Environment: am seeing the sealing errors on windows, under ibm15 and
> ibm142 jvms.
> Reporter: Mike Matrigali
> Priority: Blocker
> Attachments: derbytools_build541131.jar.out,
> derbytools_build541503.jar.out
>
>
> 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.
