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 "Patrick (JIRA)" <ji...@apache.org> on 2008/11/22 17:16:44 UTC
[jira] Closed: (DERBY-3960) Cannot start derby under jboss
[ https://issues.apache.org/jira/browse/DERBY-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick closed DERBY-3960.
--------------------------
Resolution: Duplicate
the option proposed in derby-3887 adding
JAVA_OPTS="$JAVA_OPTS -Djboss.platform.mbeanserver"
to run.conf solves the issue
> Cannot start derby under jboss
> ------------------------------
>
> Key: DERBY-3960
> URL: https://issues.apache.org/jira/browse/DERBY-3960
> Project: Derby
> Issue Type: Bug
> Affects Versions: 10.4.2.0
> Environment: Mac os X java version "1.5.0_16" Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b06-275) Java HotSpot(TM) Client VM (build 1.5.0_16-132, mixed mode, sharing)
> Reporter: Patrick
> Attachments: derby-plugin-0.0.2.jar, DerbyDatabase.java
>
>
> We use Derby with Jboss jboss-4.2.3.GA,
> to start derby we have a simple MBEAN that does
> ClassLoader cl = Thread.currentThread().getContextClassLoader();
> Class.forName(JDBC_DRIVER_CLASS, true, cl).newInstance();
> connection = DriverManager.getConnection(dbURL, user, password);
> in the past 2 years we had no problems at all with all the previous version of jboss and derby too up to 10.4.1.3
> The problems arises when we use Derby 10.4.2.0 Only! the system throws a Class Not Found Exception where try to do
> Class.forName(JDBC_DRIVER_CLASS, true, cl).newInstance();
> we tried also to recompile under the same machine 10.4.2.0 but we had the same error
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.