Unexpected Sealing Violation

[Richard Scott <gr...@archivex.net>]

Derby gurus:

I sent this to derby-user, but got no solution.  Is this a bug, or is there
a way to use the API to accomplish my needs?

I am seeing an unexpected sealing violation on
org.apache.derby.iapi.services.monitor.  There is not more than one instance
of derby.jar in the classpath (as you can verify below).

I have an application (under construction) that starts several services from
within the application.  Among these are Jetty to support a web app, and
Derby using the network server (via NetworkServerControl) instead of using
the embedded model.  These services start without incident, and as expected,
I can access the application's database externally (via ij, for instance).
However, when there's a hit on the web-app which triggers a client-side
connection to the database (using the org.apache.derby.jdbc.ClientDriver),
it barfs with "java.lang.SecurityException: sealing violation: package
org.apache.derby.iapi.services.monitor is sealed".

Can this be fixed other than by starting Derby externally to the application
(which works just fine)?

Here's what getSysinfo() spits out when after the engine is started:

Appreciate whatever enlightenment you can provide!

Richard

15:56:33 - [LtrackStartup] INFO  (DBEngine.<init>:95) - Database engine
started successfully:
--------- Derby Network Server Information --------
Version: CSS10040/10.4.1.3 - (648739)  Build: 648739  DRDA Product Id:
CSS10040
-- listing properties --
derby.drda.maxThreads=0
derby.drda.sslMode=off
derby.drda.keepAlive=true
derby.drda.minThreads=0
derby.drda.portNumber=1527
derby.drda.logConnections=true
derby.drda.timeSlice=0
derby.drda.startNetworkServer=false
derby.drda.host=127.0.0.1
derby.drda.traceAll=false
------------------ Java Information ------------------
Java Version:    1.5.0_14
Java Vendor:     Sun Microsystems Inc.
Java home:       /usr/local/jdk1.5.0_14/jre
Java classpath:
/opt/ltrack/lib/derbyclient.jar:/opt/ltrack/lib/derby.jar:/opt/ltrack/lib/derbynet.jar:/opt/ltrack/lib/derbyrun.jar:/opt/ltrack/lib/gwt-dev-linux.jar:/opt/ltrack/lib/gwt-dnd-2.5.0.jar:/opt/ltrack/lib/gwt-user.jar:/opt/ltrack/lib/gxt.jar:/opt/ltrack/lib/iaik.jar:/opt/ltrack/lib/iaik_ssl.jar:/opt/ltrack/lib/jetty-6.1.0.jar:/opt/ltrack/lib/jetty-util-6.1.0.jar:/opt/ltrack/lib/log4j.jar:/opt/ltrack/lib/ltrack.jar:/opt/ltrack/lib/ltrackUI.jar:/opt/ltrack/lib/servlet-api-2.5.jar:/opt/ltrack/lib/xercesImpl.jar:/opt/ltrack/lib/xml-apis.jar
OS name:         Linux
OS architecture: i386
OS version:      2.6.9-42.ELsmp
Java user name:  grscott
Java user home:  /home/grscott
Java user dir:   /opt/ltrack/bin
java.specification.name: Java Platform API Specification
java.specification.version: 1.5
--------- Derby Information --------
JRE - JDBC: J2SE 5.0 - JDBC 3.0
[/opt/ltrack/lib/derby.jar] 10.4.1.3 - (648739)
[/opt/ltrack/lib/derbynet.jar] 10.4.1.3 - (648739)
[/opt/ltrack/lib/derbyclient.jar] 10.4.1.3 - (648739)

Re: Unexpected Sealing Violation

[Richard Scott <gr...@archivex.net>]

Oops - my apologies for not following up here with that information in
addition to the derby-user list.  (My only excuse is I've been peddling as
hard as I can today ...)

Richard

On Thu, Oct 9, 2008 at 9:12 PM, Dag H. Wanvik <Da...@sun.com> wrote:

> Richard Scott <gr...@archivex.net> writes:
>
> > Derby gurus:
> >
> > I sent this to derby-user, but got no solution.  Is this a bug, or is
> there
> > a way to use the API to accomplish my needs?
>
> Seems this was resolved, cf. derby-user thread.
>
> Dag
>

Re: Unexpected Sealing Violation

["Dag H. Wanvik" <Da...@Sun.COM>]

Richard Scott <gr...@archivex.net> writes:

> Derby gurus:
>
> I sent this to derby-user, but got no solution.  Is this a bug, or is there
> a way to use the API to accomplish my needs?

Seems this was resolved, cf. derby-user thread.

Dag