jboss-head uses a different class loading model than 3.0.5/3.2.0RC1 so its
not clear its related to the class loading model. Create a bug report on
3.0 or 3.2 with the details of how the driver is deployed. Include any stack
traces and try to include the class loading ucl.log that results from including
this configuration in the conf/log4j.xml configuration:

<appender name="UCL" class="org.apache.log4j.FileAppender">
  <param name="File" value="${jboss.server.home.dir}/log/ucl.log"/>
  <param name="Append" value="false"/>
  <layout class="org.apache.log4j.PatternLayout">
    <param name="ConversionPattern" value="[%r,%c{1},%t] %m%n"/>
  </layout>
</appender>

<category name="org.jboss.mx.loading" additivity="false">
  <priority value="TRACE" class="org.jboss.logging.XLevel"/>
  <appender-ref ref="UCL"/>
</category>

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx

----- Original Message ----- 
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, January 17, 2003 7:50 AM
Subject: RE: [JBoss-user] Oracle / DataSource Deployment Problem with 3.0. 5


I've traced the problem to DriverManager.  In my case, I'm using mySQL, and
DriverManager has the Driver class loaded, but it skips it because it tries
to load the class from the callers ClassLoader, and class doesn't match the
class that was already loaded, so, it skips it.

So, either the caller's ClassLoader can't find the class or it finds the
class, loads it, but because the class is '!=' to the class that
DriverManager already has (i.e. it was loaded from a different codebase) it
skips it.

Looking for ClassLoading wizards to intervene and fix this.  This problem
exits not only in 3.0.5, but in jboss-head as well.  So, changes from 3.0.4
to 3.0.5 and recent jboss-head changes are causing this problem.

Thanks,
Michael




-------------------------------------------------------
This SF.NET email is sponsored by: Thawte.com - A 128-bit supercerts will
allow you to extend the highest allowed 128 bit encryption to all your 
clients even if they use browsers that are limited to 40 bit encryption. 
Get a guide here:http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0030en
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to