From users-return-242979-apmail-tomcat-users-archive=tomcat.apache.org@tomcat.apache.org Fri Aug 2 19:25:06 2013 Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6F93910267 for ; Fri, 2 Aug 2013 19:25:06 +0000 (UTC) Received: (qmail 77366 invoked by uid 500); 2 Aug 2013 19:25:03 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 77275 invoked by uid 500); 2 Aug 2013 19:25:02 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 77266 invoked by uid 99); 2 Aug 2013 19:25:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Aug 2013 19:25:02 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [207.211.31.74] (HELO service89-us.mimecast.com) (207.211.31.74) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Aug 2013 19:24:56 +0000 Received: from loftexchange.loftwareinc.com (WPIS-64-140-236-129.worldpath.net [64.140.236.129]) (Using TLS) by service89-us.mimecast.com; Fri, 02 Aug 2013 15:24:35 -0400 Received: from loftexchange.loftwareinc.com ([172.16.40.3]) by loftexchange.loftwareinc.com ([172.16.40.3]) with mapi; Fri, 2 Aug 2013 15:24:34 -0400 From: To: Date: Fri, 2 Aug 2013 15:24:32 -0400 Subject: 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: Ac6PtavE/B2iWyACRESD1YDBtI48AA== Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US MIME-Version: 1.0 X-MC-Unique: 113080215243501701 Content-Type: multipart/alternative; boundary="_000_A1F4506ED573C34F92D5E3B1686494A84E7FB83904loftexchangel_" X-Virus-Checked: Checked by ClamAV on apache.org --_000_A1F4506ED573C34F92D5E3B1686494A84E7FB83904loftexchangel_ Content-Type: text/plain; charset=WINDOWS-1252 Content-Transfer-Encoding: quoted-printable I expect that by putting the SQL Server JDBC4 driver jar (sqljdbc4.jar) int= o ${CATALINA_HOME}/lib, that the driver would be automatically available up= on 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, setti= ng driverManagerProtection to false in the JreMemoryLeakPreventionListener = allows this to work in 6.0.35 as well. I would not have expected that a ch= ange 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 exactl= y why this is happening. The MySQL driver loads without any issue. I am wondering if anyone else has seen this problem. Thanks, Mark --_000_A1F4506ED573C34F92D5E3B1686494A84E7FB83904loftexchangel_--