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 "David Van Couvering (JIRA)" <de...@db.apache.org> on 2006/03/17 22:00:47 UTC
[jira] Created: (DERBY-1125) Getting security exception because
classes in iapi.services.info have been added to derbyclient.jar
Getting security exception because classes in iapi.services.info have been added to derbyclient.jar
---------------------------------------------------------------------------------------------------
Key: DERBY-1125
URL: http://issues.apache.org/jira/browse/DERBY-1125
Project: Derby
Type: Bug
Reporter: David Van Couvering
>From Andrew's email:
On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> </snip a whole bunch of stuff>
>
> Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
already loaded
See DERBY-848 and DERBY-1046.
iapi.services.info.ProductVersionHolder and friends were added to
derbyclient.jar by David in DERBY-848, specifically with revision
370815.
There are two clear solutions: unseal iapi.services.info or copy the
info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1125) Getting security exception because
classes in iapi.services.info have been added to derbyclient.jar
Posted by "Andrew McIntyre (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1125?page=comments#action_12370911 ]
Andrew McIntyre commented on DERBY-1125:
----------------------------------------
I agree, option 1 is the way to go.
I remembered after you brought it up in option 3 above that currently the code is already duplicated in the tools jar. It is assumed that the network server will be running alongside the engine, so classlister filters out the info classes from derbynet.jar.
These classes are fairly stable. JVMInfo is the only one that has seen any change, and that was to add a new identifier for JDK 1.6. That change was made in 10.2. The potential for problems with shadowing, etc. are already there with the duplication in derbytools.jar, I suppose, but I think the potential for problems is minor, and the problem in a mixed environment would be fairly obvious to spot.
> Getting security exception because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-1125
> URL: http://issues.apache.org/jira/browse/DERBY-1125
> Project: Derby
> Type: Bug
> Reporter: David Van Couvering
> Assignee: David Van Couvering
>
> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1125) Getting security exception when
derbyclient.jar is before derby.jar because classes in iapi.services.info
have been added to derbyclient.jar
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1125?page=all ]
Kathey Marsden updated DERBY-1125:
----------------------------------
Component: Build tools
> Getting security exception when derbyclient.jar is before derby.jar because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1125
> URL: http://issues.apache.org/jira/browse/DERBY-1125
> Project: Derby
> Type: Bug
> Components: Build tools
> Versions: 10.2.0.0
> Reporter: David Van Couvering
> Assignee: David Van Couvering
> Priority: Critical
> Fix For: 10.2.0.0
>
> This security exception can occur if derbyclient.jar is before derby.jar after revision 370815.
> See:
> http://www.nabble.com/regression-%21-all-tests-in-jdbcapi-fails-for-me-t1298249.html#a3462544
> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DERBY-1125) Getting security exception when
derbyclient.jar is before derby.jar because classes in iapi.services.info
have been added to derbyclient.jar
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1125?page=all ]
Kathey Marsden updated DERBY-1125:
----------------------------------
Summary: Getting security exception when derbyclient.jar is before derby.jar because classes in iapi.services.info have been added to derbyclient.jar (was: Getting security exception because classes in iapi.services.info have been added to derbyclient.jar)
Fix Version: 10.2.0.0
Description:
This security exception can occur if derbyclient.jar is before derby.jar after revision 370815.
See:
http://www.nabble.com/regression-%21-all-tests-in-jdbcapi-fails-for-me-t1298249.html#a3462544
>From Andrew's email:
On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> </snip a whole bunch of stuff>
>
> Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
already loaded
See DERBY-848 and DERBY-1046.
iapi.services.info.ProductVersionHolder and friends were added to
derbyclient.jar by David in DERBY-848, specifically with revision
370815.
There are two clear solutions: unseal iapi.services.info or copy the
info classes to a new shared info package.
was:
>From Andrew's email:
On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> </snip a whole bunch of stuff>
>
> Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
already loaded
See DERBY-848 and DERBY-1046.
iapi.services.info.ProductVersionHolder and friends were added to
derbyclient.jar by David in DERBY-848, specifically with revision
370815.
There are two clear solutions: unseal iapi.services.info or copy the
info classes to a new shared info package.
Version: 10.2.0.0
Priority: Critical (was: Major)
> Getting security exception when derbyclient.jar is before derby.jar because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1125
> URL: http://issues.apache.org/jira/browse/DERBY-1125
> Project: Derby
> Type: Bug
> Versions: 10.2.0.0
> Reporter: David Van Couvering
> Assignee: David Van Couvering
> Priority: Critical
> Fix For: 10.2.0.0
>
> This security exception can occur if derbyclient.jar is before derby.jar after revision 370815.
> See:
> http://www.nabble.com/regression-%21-all-tests-in-jdbcapi-fails-for-me-t1298249.html#a3462544
> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1125) Getting security exception because
classes in iapi.services.info have been added to derbyclient.jar
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1125?page=comments#action_12371345 ]
Kathey Marsden commented on DERBY-1125:
---------------------------------------
I am coming into this issue late so might really be misunderstanding things but I don't like this idea of importing engine classes into the client no matter how stable we think they are. Doing this means that every line of code has to be evaluated for impact.
This strategy was discussed on the list previously and the concensus I thought was that for client a copy would be put in the shared directory and at such time as we had a code sharing solution, the files would be combined. If the files are really that stable it shouldn't be hard to resolve differences.
Also, the description of this bug does not describe the circumstances under which a user might see this issue. I seem to recall that it imposed some sort of required classpath order. Is that correct?
If so I think it is a regression and needs to be moved up to Blocker for 10.2.
> Getting security exception because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-1125
> URL: http://issues.apache.org/jira/browse/DERBY-1125
> Project: Derby
> Type: Bug
> Reporter: David Van Couvering
> Assignee: David Van Couvering
>
> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1125) Getting security exception because
classes in iapi.services.info have been added to derbyclient.jar
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1125?page=comments#action_12371349 ]
David Van Couvering commented on DERBY-1125:
--------------------------------------------
Hi, Kathey, I was wondering when you were going to join in on the fun :)
The thing is, that these classes have been imported into the client jar for as long as I have been on the project. So I can't imagine it can be a regression to put it back the way things were.
If you don't like the solution of reverting back to how things were, can you suggest another one?
Thanks,
David
> Getting security exception because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-1125
> URL: http://issues.apache.org/jira/browse/DERBY-1125
> Project: Derby
> Type: Bug
> Reporter: David Van Couvering
> Assignee: David Van Couvering
>
> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DERBY-1125) Getting security exception when
derbyclient.jar is before derby.jar because classes in iapi.services.info
have been added to derbyclient.jar
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1125?page=all ]
David Van Couvering resolved DERBY-1125:
----------------------------------------
Resolution: Fixed
Committed revision 387905
> Getting security exception when derbyclient.jar is before derby.jar because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1125
> URL: http://issues.apache.org/jira/browse/DERBY-1125
> Project: Derby
> Type: Bug
> Versions: 10.2.0.0
> Reporter: David Van Couvering
> Assignee: David Van Couvering
> Priority: Critical
> Fix For: 10.2.0.0
>
> This security exception can occur if derbyclient.jar is before derby.jar after revision 370815.
> See:
> http://www.nabble.com/regression-%21-all-tests-in-jdbcapi-fails-for-me-t1298249.html#a3462544
> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DERBY-1125) Getting security exception when
derbyclient.jar is before derby.jar because classes in iapi.services.info
have been added to derbyclient.jar
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1125?page=all ]
David Van Couvering closed DERBY-1125:
--------------------------------------
> Getting security exception when derbyclient.jar is before derby.jar because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1125
> URL: http://issues.apache.org/jira/browse/DERBY-1125
> Project: Derby
> Type: Bug
> Components: Build tools
> Versions: 10.2.0.0
> Reporter: David Van Couvering
> Assignee: David Van Couvering
> Priority: Critical
> Fix For: 10.2.0.0
>
> This security exception can occur if derbyclient.jar is before derby.jar after revision 370815.
> See:
> http://www.nabble.com/regression-%21-all-tests-in-jdbcapi-fails-for-me-t1298249.html#a3462544
> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (DERBY-1125) Getting security exception because
classes in iapi.services.info have been added to derbyclient.jar
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1125?page=all ]
David Van Couvering reassigned DERBY-1125:
------------------------------------------
Assign To: David Van Couvering
> Getting security exception because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-1125
> URL: http://issues.apache.org/jira/browse/DERBY-1125
> Project: Derby
> Type: Bug
> Reporter: David Van Couvering
> Assignee: David Van Couvering
>
> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1125) Getting security exception because
classes in iapi.services.info have been added to derbyclient.jar
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1125?page=comments#action_12371352 ]
David Van Couvering commented on DERBY-1125:
--------------------------------------------
Also, to answer your question, yes, my understanding is that the bug reveals itself when derbyclient.jar is in front of derby.jar. Please feel free to upgrade to Blocker. I was working on implementing Solution 1 as described above but I'm on hold now until we can finish our discussion of potential issues around this solution and what the best alternative might be, if any.
> Getting security exception because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-1125
> URL: http://issues.apache.org/jira/browse/DERBY-1125
> Project: Derby
> Type: Bug
> Reporter: David Van Couvering
> Assignee: David Van Couvering
>
> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1125) Getting security exception because
classes in iapi.services.info have been added to derbyclient.jar
Posted by "Kathey Marsden (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1125?page=comments#action_12371361 ]
Kathey Marsden commented on DERBY-1125:
---------------------------------------
Thanks David, that is my mistake. I did not realize that this was part of the sysinfo code imported into client in 10.1. Please go ahead and switch it back to the 10.1 setup.
The defect itself is a regression because a classpath order that worked in 10.1 derbyclient.jar;derby.jar does not currently work in 10.2. I found the mail:
http://www.nabble.com/regression-%21-all-tests-in-jdbcapi-fails-for-me-t1298249.html#a3462544
I'll bump it up to Critical I guess. But a must fix for 10.2 I think. As we get closer to the release I think it is important that product regressions be properly identified and not slip through the cracks so that is why I brought it up.
Thanks for taking care of this issue.
> Getting security exception because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-1125
> URL: http://issues.apache.org/jira/browse/DERBY-1125
> Project: Derby
> Type: Bug
> Reporter: David Van Couvering
> Assignee: David Van Couvering
>
> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DERBY-1125) Getting security exception because
classes in iapi.services.info have been added to derbyclient.jar
Posted by "David Van Couvering (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1125?page=comments#action_12370904 ]
David Van Couvering commented on DERBY-1125:
--------------------------------------------
OK, to be clear, what happened was not that I included the iapi/services/info package, that has been there for a while.
What happened was I *copied* JVMInfo from iapi/services/info to shared/common/info. At that time I was unaware that iapi/services/info was being included in derbyclient.jar.
Then Knut discovered that JVMInfo was in two places in derbyclient.jar (iapi/services/info and shared/common/info), so I then excluded services/info/JVMInfo.class from the derbyclient jar file. Case solved (hah!).
So now what happens is that services/info/JVMInfo is loaded from derby.jar when you run with derby.jar and derbyclient.jar in the same classpath. And then if you have derbyclient.jar in from of derby.jar all other classes from the package services/info are loaded from derbyclient.jar. This is not allowed for sealed packages, thus the security exception.
I made my copy of JVMInfo because I had assumed it was a Bad Thing to copy the same classes into two separate jar files. This is called Code Sharing and is Not Allowed. But it's been there for quite a while. So in a mixed version environment you can have the same shadowing/compatibility issues that have been painstakingly documented for code sharing in general.
So, we have the following choices:
(1) I can remove the copy of JVMInfo in shared/common/info, and go back to the way things were. In my client code I can import org.apache.derby.iapi.services.info.JVMInfo instead of org.apache.derby.shared.common.info.JVMInfo. This is the way things were and would probably be the simplest solution, but we would continue to have the potential issues around compatibility and shadowing in a mixed version environment. It is worth noting that this has not come up as an issue as of yet.
(2) I can copy everything into org.apache.derby.shared.common and fix all client code so it refers to the shared versions of this stuff. The risk of this is now we have a fair amount of code duplication, and things can get skewed pretty easily
(3) I can implement the proposal we had earlier, which was to use a build script to automatically make a copy of the classes in iapi/services/info and put them in shared. The engine code would continue to use iapi/services/info, and the client code would use shared/common/info. I do have to wonder what is going on with the tools and network jar files, however, as I think they are also making use of iapi/services/info classes. This could turn into a Big Project if I have to make copies for each jar file.
(4) Unseal iapi/services/info. This seems like the wrong way to go. This is an internal package and we don't want it to be possible to interject "new" implementations of these classes from other code bases.
My current itch is to put things back the way they were, and solve the longer-term code sharing problem as part of the code sharing JIRA, DERBY-289. So I am going to go with option (1). But please let me know if you have an opinion on this.
> Getting security exception because classes in iapi.services.info have been added to derbyclient.jar
> ---------------------------------------------------------------------------------------------------
>
> Key: DERBY-1125
> URL: http://issues.apache.org/jira/browse/DERBY-1125
> Project: Derby
> Type: Bug
> Reporter: David Van Couvering
> Assignee: David Van Couvering
>
> From Andrew's email:
> On 3/17/06, Andreas Korneliussen <An...@sun.com> wrote:
> > </snip a whole bunch of stuff>
> >
> > Exception: java.lang.SecurityException: sealing violation: can't seal package org.apache.derby.iapi.services.info:
> already loaded
> See DERBY-848 and DERBY-1046.
> iapi.services.info.ProductVersionHolder and friends were added to
> derbyclient.jar by David in DERBY-848, specifically with revision
> 370815.
> There are two clear solutions: unseal iapi.services.info or copy the
> info classes to a new shared info package.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira