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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2011/08/16 14:39:27 UTC
[jira] [Commented] (DERBY-4634) Error Message when launching Derby
(SEVERE JDBC ERROR)
[ https://issues.apache.org/jira/browse/DERBY-4634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13085663#comment-13085663 ]
Kristian Waagan commented on DERBY-4634:
----------------------------------------
Any updates on this?
If we hear nothing more, we should probably close the issue.
> Error Message when launching Derby (SEVERE JDBC ERROR)
> ------------------------------------------------------
>
> Key: DERBY-4634
> URL: https://issues.apache.org/jira/browse/DERBY-4634
> Project: Derby
> Issue Type: Bug
> Components: Eclipse Plug-in, JDBC
> Affects Versions: 10.5.3.0
> Environment: Windows, Eclipse 3.2.2, Derby 10.5.3.0
> Reporter: michael jerusalmi
> Priority: Minor
> Labels: bug, derby, derby_triage10_8, jdbc, network, oracle, server, severe, starting
>
> 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.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira