You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Mike Matrigali (JIRA)" <ji...@apache.org> on 2007/05/26 14:09:17 UTC
[jira] Created: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
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.
[jira] Updated: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-2701:
--------------------------------------
Attachment: 2701-3.diff
Would it make sense to seal org.apache.derby.iapi.error and org.apache.derby.impl.jdbc now that derby.jar is the only jar file which contains classes from those packages? Attaching patch (2701-3) which modifies build.xml so that those packages are sealed.
> 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
> Assigned To: Knut Anders Hatlen
> Priority: Blocker
> Attachments: 2701-2.diff, 2701-3.diff, derby2701.diff, derbytools_build541131.jar.out, derbytools_build541503.jar.out, dobuilds2.ksh
>
>
> 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.
[jira] Updated: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-2701:
----------------------------------
Attachment: derbytools_build541131.jar.out
derbytools_build541131.jar.out is the output of jar -tvf on a derbytools.jar build as of 541131
> 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
> Attachments: derbytools_build541131.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.
[jira] Closed: (DERBY-2701) many sealing violation errors in ibm142
and ibm15 jvm test runs of junit tests.
Posted by "Dyre Tjeldvoll (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dyre Tjeldvoll closed DERBY-2701.
---------------------------------
> 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, Tools
> Affects Versions: 10.3.1.4
> Environment: am seeing the sealing errors on windows, under ibm15 and ibm142 jvms.
> Reporter: Mike Matrigali
> Assignee: Knut Anders Hatlen
> Priority: Blocker
> Fix For: 10.3.1.4
>
> Attachments: 2701-2.diff, 2701-3.diff, derby2701.diff, derbytools_build541131.jar.out, derbytools_build541503.jar.out, dobuilds2.ksh
>
>
> 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.
[jira] Updated: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-2701:
----------------------------------
>From doing builds it looks like the following change caused the derbytools.jar bloat. Again I have no idea if the change is wrong, or if the change just added new requirements to the tools that build the jar files:
------------------------------------------------------------------------
r541435 | kahatlen | 2007-05-24 14:21:27 -0700 (Thu, 24 May 2007) | 37 lines
DERBY-1440: jdk 1.6 client driver omits SQLStates and chained exceptions in
error messages
While working on DERBY-2472 I found out what caused this difference between
the JDBC 3.0 driver and the JDBC 4.0 driver. There are three
problems. Firstly, StandardException.unexpectedUserException() doesn't
recognize that an SQLException is generated Derby since it is not an
EmbedSQLException. Secondly, TransactionResourceImpl.wrapInSQLException()
invokes SQLException.setNextException() explicitly so that the required
chaining/ferrying logic in the exception factory and in EmbedSQLException's
constructor is not used. Thirdly,
SQLException40.wrapArgsForTransportAcrossDRDA() puts a standard
SQLException, not an EmbedSQLException, in the argument ferry's
next-exception chain, which prevents the network server from seeing it as a
Derby exception.
The attached patch fixes the problem by
1) using SQLExceptionFactory.getArgumentFerry() to find out whether the
exception is a Derby exception in unexpectedUserException()
2) using factory methods instead of setNextException() to do the chaining
in wrapInSQLException()
3) improving Util.javaException() so that it sets up a next-exception
chain if the Java exception contains nested exceptions
4) changing wrapArgsForTransportAcrossDRDA() to create an argument ferry
whose next exception is the argument ferry of the main exception's next
exception
This patch also fixes all the JUnit tests that contain code looking like this:
assertStatementError(JDBC.vmSupportsJDBC4() ? "38000" : "42X62", cSt);
Now, the check for JDBC level is not needed anymore for those tests.
------------------------------------------------------------------------
U java\engine\org\apache\derby\impl\jdbc\EmbedResultSet.java
U java\engine\org\apache\derby\impl\jdbc\SQLExceptionFactory40.java
U java\engine\org\apache\derby\impl\jdbc\Util.java
U java\engine\org\apache\derby\impl\jdbc\TransactionResourceImpl.java
U java\engine\org\apache\derby\iapi\error\StandardException.java
U java\engine\org\apache\derby\jdbc\EmbedXAResource.java
U java\testing\org\apache\derbyTesting\functionTests\tests\lang\XMLTypeAndOpsTest.java
U java\testing\org\apache\derbyTesting\functionTests\tests\lang\SysDiagVTIMappingTest.java
U java\testing\org\apache\derbyTesting\functionTests\tests\lang\ProcedureInTriggerTest.java
U java\testing\org\apache\derbyTesting\functionTests\tests\tools\ImportExportLobTest.java
U java\testing\org\apache\derbyTesting\functionTests\tests\tools\ImportExportBinaryDataTest.java
U java\testing\org\apache\derbyTesting\functionTests\tests\tools\ImportExportTest.java
Updated to revision 541410.
> 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.
[jira] Commented: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499379 ]
Myrna van Lunteren commented on DERBY-2701:
-------------------------------------------
Unfortunately, I see the same error after applying the patch...
> 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: derby2701.diff, derbytools_build541131.jar.out, derbytools_build541503.jar.out, dobuilds2.ksh
>
>
> 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.
[jira] Resolved: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen resolved DERBY-2701.
---------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Sealed the two packages and committed revision 542155.
> 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, Tools
> Affects Versions: 10.3.0.0
> Environment: am seeing the sealing errors on windows, under ibm15 and ibm142 jvms.
> Reporter: Mike Matrigali
> Assignee: Knut Anders Hatlen
> Priority: Blocker
> Fix For: 10.3.0.0
>
> Attachments: 2701-2.diff, 2701-3.diff, derby2701.diff, derbytools_build541131.jar.out, derbytools_build541503.jar.out, dobuilds2.ksh
>
>
> 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.
[jira] Commented: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499314 ]
Knut Anders Hatlen commented on DERBY-2701:
-------------------------------------------
FWIW, I noticed the same thing on OpenSolaris and Sun Java 1.5/1.6 with insane jars. It worked when I switched to sane jars.
> 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.
[jira] Commented: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499402 ]
Knut Anders Hatlen commented on DERBY-2701:
-------------------------------------------
The 2701-2 patch removed the sealing violation problem on my machine.
Committed revision 541977.
> 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
> Assigned To: Knut Anders Hatlen
> Priority: Blocker
> Attachments: 2701-2.diff, derby2701.diff, derbytools_build541131.jar.out, derbytools_build541503.jar.out, dobuilds2.ksh
>
>
> 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.
[jira] Updated: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-2701:
----------------------------------
Attachment: derbytools_build541503.jar.out
derbytools_build541503.jar.out is the output of a jar -tvf on a derbytools.jar build from 541503
> 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
> 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.
[jira] Commented: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Myrna van Lunteren (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12499377 ]
Myrna van Lunteren commented on DERBY-2701:
-------------------------------------------
I could duplicate the behavior on my machine. I'm trying out the patch and will report back.
> 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: derby2701.diff, derbytools_build541131.jar.out, derbytools_build541503.jar.out, dobuilds2.ksh
>
>
> 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.
[jira] Updated: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-2701:
----------------------------------
Attachment: dobuilds2.ksh
in case anyone is interested here is the crude ksh script I used to do builds on a per change basis. I got
the changes by hand but there must be some magic svn and sed I could have done to get the list between
2 changes.
Someday I would like a script to do a set of builds and run a test to see what change introduced a bug. Tinderbox is very useful, but often more than one change goes into a tinderbox run.
you may have to fiddle with the cd's and ant commands to get it to work in your env.
> 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, dobuilds2.ksh
>
>
> 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.
[jira] Updated: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-2701:
--------------------------------------
Attachment: 2701-2.diff
Thanks for narrowing it down, Mike!
I think the real problem is that derbytools.jar should not reference StandardException in the first place. It seems like it only uses it where it accesses JDBC 3.0 methods via reflection. The attached patch makes utilMain.java call JDBC 3.0 methods directly and removes the import of StandardException. I haven't tested the patch yet, but it does remove these classes from derbytools.jar compared to revision 541131:
9,11d8
< org/apache/derby/iapi/error/PublicAPI.class
< org/apache/derby/iapi/error/StandardException$BadMessageArgumentException.class
< org/apache/derby/iapi/error/StandardException.class
21d17
< org/apache/derby/impl/jdbc/EmbedSQLException.class
> 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
> Assigned To: Knut Anders Hatlen
> Priority: Blocker
> Attachments: 2701-2.diff, derby2701.diff, derbytools_build541131.jar.out, derbytools_build541503.jar.out, dobuilds2.ksh
>
>
> 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.
[jira] Updated: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-2701:
----------------------------------
Attachment: derby2701.diff
derby2701.diff creates a derbytools.jar that is a lot smaller. I have not run any tests, as I have not actually been able to reproduce the sealing violation problem on my machine. The change is to add to the list of packages
that this tool was already explicitly not includeing for derbytools.jar.
If anyone can reproduce the current problem and then apply this and see if it fixes it, let me 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: derby2701.diff, derbytools_build541131.jar.out, derbytools_build541503.jar.out, dobuilds2.ksh
>
>
> 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.
[jira] Updated: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-2701:
----------------------------------
Environment: am seeing the sealing errors on windows, under ibm15 and ibm142 jvms.
Am only seeing errors in the junit suite run. Derbyall finishes either all clean or mostly clean, no sealing errors.
> 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.
[jira] Updated: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Mike Matrigali (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Matrigali updated DERBY-2701:
----------------------------------
I narrowed down the problem to just the changes to these 2 files:
M java/engine/org/apache/derby/impl/jdbc/Util.java
M java/engine/org/apache/derby/iapi/error/StandardException.java
The change to StandardException adds an import:
import org.apache.derby.impl.jdbc.Util;
The class already had an import to another impl file:
import org.apache.derby.impl.jdbc.EmbedSQLException;
The util file goes on to import stuff from there.
I verified that if I comment out the import in StandardException.java and the code that uses it then the derbytools.jar shrinks.
> 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, dobuilds2.ksh
>
>
> 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.
[jira] Assigned: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen reassigned DERBY-2701:
-----------------------------------------
Assignee: Knut Anders Hatlen
> 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
> Assigned To: Knut Anders Hatlen
> Priority: Blocker
> Attachments: derby2701.diff, derbytools_build541131.jar.out, derbytools_build541503.jar.out, dobuilds2.ksh
>
>
> 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.
[jira] Updated: (DERBY-2701) many sealing violation errors in
ibm142 and ibm15 jvm test runs of junit tests.
Posted by "Knut Anders Hatlen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Knut Anders Hatlen updated DERBY-2701:
--------------------------------------
Component/s: Tools
> 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, Tools
> Affects Versions: 10.3.0.0
> Environment: am seeing the sealing errors on windows, under ibm15 and ibm142 jvms.
> Reporter: Mike Matrigali
> Assigned To: Knut Anders Hatlen
> Priority: Blocker
> Attachments: 2701-2.diff, 2701-3.diff, derby2701.diff, derbytools_build541131.jar.out, derbytools_build541503.jar.out, dobuilds2.ksh
>
>
> 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.