[DERBY-4634] Error Message when launching Derby (SEVERE JDBC ERROR)

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.5.3.0
• Component/s: Eclipse Plug-in, JDBC
• Labels: bug derby derby_triage10_8 jdbc network oracle server severe starting
• Environment: Windows, Eclipse 3.2.2, Derby 10.5.3.0
• Urgency: Low
• Assignee: Unassigned
• Reporter: michael jerusalmi
• Created: 28/Apr/10 10:23
• Updated: 16/Aug/11 12:37

Description

I've been using Derby for a few days without any problems.
But when I started Eclipse this morning, everytime I try to start Derby Network Server, I got this message :

28 avr. 2010 12:06:21 oracle.jdbc.driver.OracleDriver registerMBeans
SEVERE: Error while registering Oracle JDBC Diagnosability MBean.
java.security.AccessControlException: access denied (javax.management.MBeanServerPermission createMBeanServer)
at java.security.AccessControlContext.checkPermission(Unknown Source)
at java.security.AccessController.checkPermission(Unknown Source)
at java.lang.SecurityManager.checkPermission(Unknown Source)
at java.lang.management.ManagementFactory.getPlatformMBeanServer(Unknown Source)
at oracle.jdbc.driver.OracleDriver.registerMBeans(OracleDriver.java:306)
at oracle.jdbc.driver.OracleDriver$1.run(OracleDriver.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.jdbc.driver.OracleDriver.<clinit>(OracleDriver.java:193)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at sun.misc.Service$LazyIterator.next(Unknown Source)
at java.sql.DriverService.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.sql.DriverManager.loadInitialDrivers(Unknown Source)
at java.sql.DriverManager.initialize(Unknown Source)
at java.sql.DriverManager.registerDriver(Unknown Source)
at org.apache.derby.jdbc.AutoloadedDriver.<clinit>(Unknown Source)
at org.apache.derby.jdbc.Driver20.boot(Unknown Source)
at org.apache.derby.jdbc.Driver40.boot(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.boot(Unknown Source)
at org.apache.derby.impl.services.monitor.TopService.bootModule(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.bootService(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.startServices(Unknown Source)
at org.apache.derby.impl.services.monitor.BaseMonitor.runWithState(Unknown Source)
at org.apache.derby.impl.services.monitor.FileMonitor.<init>(Unknown Source)
at org.apache.derby.iapi.services.monitor.Monitor.startMonitor(Unknown Source)
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)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.apache.derby.impl.drda.NetworkServerControlImpl.startNetworkServer(Unknown Source)
at org.apache.derby.impl.drda.NetworkServerControlImpl.blockingStart(Unknown Source)
at org.apache.derby.impl.drda.NetworkServerControlImpl.executeWork(Unknown Source)
at org.apache.derby.drda.NetworkServerControl.main(Unknown Source)

And even though, Derby seems to be launched as I got the message :
2010-04-28 10:06:21.689 GMT : Apache Derby network Server - 10.5.3.0 - (802917) started and ready to accept connections on port 1527

It's not a bolcking problem, as my WebApp is still working, but I've never seen it before.

Issue Links

• is related to: DERBY-3887 Embedded Derby fails under JBoss because of JMX-related conflicts