Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1586491521.1227369524333.JavaMail.jira@brutus>
Date: Sat, 22 Nov 2008 07:58:44 -0800 (PST)
From: "Patrick (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-3960) Cannot start derby under jboss
In-Reply-To: <642080482.1227364484384.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


     [ https://issues.apache.org/jira/browse/DERBY-3960?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Patrick updated DERBY-3960:
---------------------------

    Attachment: DerbyDatabase.java
                derby-plugin-0.0.2.jar

the mbean used to start derby=20

> 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) C=
lient VM (build 1.5.0_16-132, mixed mode, sharing)     =20
>            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=20
> ClassLoader cl =3D Thread.currentThread().getContextClassLoader();
> Class.forName(JDBC_DRIVER_CLASS, true, cl).newInstance();
> connection =3D DriverManager.getConnection(dbURL, user, password);
> in the past 2 years we had no problems at all with all the previous versi=
on of jboss and derby too up to 10.4.1.3=20
> The problems arises when we use Derby 10.4.2.0 Only!  the system throws a=
 Class Not Found Exception where try to do=20
> =C2=A0Class.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

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.