Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
From: <MWick@loftware.com>
To: <users@tomcat.apache.org>
Date: Tue, 6 Aug 2013 07:57:55 -0400
Subject: RE: Auto-loading of the SQL Server JDBC Driver in 6.0.35
Thread-Topic: Auto-loading of the SQL Server JDBC Driver in 6.0.35
Thread-Index: Ac6R07Fg6a6ps7RkTp6XW8sFj14nfgAx8ISg
Message-ID: 
 <A1F4506ED573C34F92D5E3B1686494A84E7FB83AFB@loftexchange.loftwareinc.com>
References: 
 <A1F4506ED573C34F92D5E3B1686494A84E7FB83904@loftexchange.loftwareinc.com>
 <51FC082B.7000407@gmx.net>
 <A1F4506ED573C34F92D5E3B1686494A84E7FB8392B@loftexchange.loftwareinc.com>
 <51FC2472.1010704@yahoo.com>
 <A1F4506ED573C34F92D5E3B1686494A84E7FB8394B@loftexchange.loftwareinc.com>
 <7BF5C878-1E3A-4293-B6AF-881FB8F80C7D@gopivotal.com>
In-Reply-To: <7BF5C878-1E3A-4293-B6AF-881FB8F80C7D@gopivotal.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
MIME-Version: 1.0
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable

> From: Daniel Mikusa [mailto:dmikusa@gopivotal.com]
> Sent: Monday, August 05, 2013 7:56 AM
> To: Tomcat Users List
> Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35
>=20
> On Aug 4, 2013, at 2:14 PM, MWick@loftware.com wrote:
>=20
> >> From: Mark Eggers [mailto:its_toasted@yahoo.com]
> >> Sent: Friday, August 02, 2013 5:28 PM
> >> To: Tomcat Users List
> >> Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35
> >>
> >> On 8/2/2013 1:30 PM, MWick@loftware.com wrote:
> >>>> From: Michael-O [mailto:1983-01-06@gmx.net] Sent: Friday, August
> >>>> 02,
> >>>> 2013 3:28 PM To: Tomcat Users List Subject: Re: Auto-loading of the
> >>>> SQL Server JDBC Driver in 6.0.35
> >>>>
> >>>> Am 2013-08-02 21:24, schrieb MWick@loftware.com:
> >>>>> I expect that by putting the SQL Server JDBC4 driver jar
> >>>>> (sqljdbc4.jar) into ${CATALINA_HOME}/lib, that the driver would be
> >>>>> automatically available upon server start.  As expected, this
> >>>>> works in 6.0.33, but fails in 6.0.35.  It seems that the fix to
> >>>>> Bug 51640 is the cause of this, and in fact, setting
> >>>>> driverManagerProtection to false in the
> >>>>> JreMemoryLeakPreventionListener allows this to work in 6.0.35 as
> >>>>> well.  I would not have expected that a change to the MemoryLeak
> >>>>> Listener would have changed the behavior of the JDBC driver.
> >>>>>
> >>>>> I don't know the internals of the SQL Server driver, so I don't
> >>>>> know exactly why this is happening.  The MySQL driver loads
> >>>>> without any issue.
> >>>>
> >>>> Why should the driver being loaded into memory if no one uses it?
> >>>> Actually, a driver is loaded into the container's classloader cache
> >>>> upon first access. This is what happens at least for me with the
> >>>> Oracle driver.
> >>>>
> >>>> Everything else does not make sense to me.
> >>>>
> >>>> Michael
> >>>
> >>> Sorry, I wasn't clear.  It's not loading the driver into memory, but
> >>> rather registering it with the DriverManager that has changed, so
> >>> that it can be loaded on the first request.  This is no longer occurr=
ing.
> >>>
> >>> Mark
> >>
> >> How are you accessing the driver?
> >>
> >> Are you using JDBC directly, or are you creating a JNDI pooled
> >> connection and letting Tomcat manage it.
> >>
> >> . . . . just my two questions
> >> /mde/
> >
> > Using the Apache JDBC pool with DataSources, but directly.
>=20
> Are you specifying a "driverClassName"?  If you specify that and the JDBC
> driver is available on the class path then the pool should just work.  No=
 need
> to call DriverManager or load classes.  The pool should handle that for y=
ou.
>=20
> See example for using the pool from Java.
>=20
>    http://tomcat.apache.org/tomcat-7.0-doc/jdbc-pool.html#Plain_Ol'_Java
>=20
> Dan
>

No.   And there is no need.  Type 4 JDBC drivers are supposed to register a=
utomatically.  I have created a simple test; copying the Oracle, SQL*Server=
 and MySQL drivers into ${CATALINA_HOME}/lib; starting Tomcat and then runn=
ing a method that prints out the registered drivers (from DriverManager.get=
Drivers()).   With the default line below in server.xml, only the JdbcOdbc =
bridge driver is registered.

<Listener className=3D"org.apache.catalina.core.JreMemoryLeakPreventionList=
ener" />

Driver Class
sun.jdbc.odbc.JdbcOdbcDriver

However, if I disable "driver manager protection" - effectively turn off th=
e fix for 51640, as shown below, the JdbcOdbc bridge AND the 3 other driver=
s are all listed as registered.  I will file a bug.

<Listener className=3D"org.apache.catalina.core.JreMemoryLeakPreventionList=
ener" driverManagerProtection=3D"false" />


Driver Class
sun.jdbc.odbc.JdbcOdbcDriver=20
com.mysql.jdbc.Driver=20
oracle.jdbc.OracleDriver=20
com.microsoft.sqlserver.jdbc.SQLServerDriver


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org