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 B524C10279 for ; Fri, 2 Aug 2013 19:28:09 +0000 (UTC) Received: (qmail 88879 invoked by uid 500); 2 Aug 2013 19:28:06 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 88749 invoked by uid 500); 2 Aug 2013 19:28:06 -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 88739 invoked by uid 99); 2 Aug 2013 19:28:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Aug 2013 19:28:06 +0000 X-ASF-Spam-Status: No, hits=0.8 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FROM_STARTS_WITH_NUMS,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of 1983-01-06@gmx.net designates 212.227.17.21 as permitted sender) Received: from [212.227.17.21] (HELO mout.gmx.net) (212.227.17.21) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Aug 2013 19:27:59 +0000 Received: from [192.168.1.4] ([93.219.116.71]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0M2ojS-1UEClB2gg2-00siMY for ; Fri, 02 Aug 2013 21:27:39 +0200 Message-ID: <51FC082B.7000407@gmx.net> Date: Fri, 02 Aug 2013 21:27:39 +0200 From: Michael-O <1983-01-06@gmx.net> User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130620 Thunderbird/17.0.7 MIME-Version: 1.0 To: Tomcat Users List Subject: Re: Auto-loading of the SQL Server JDBC Driver in 6.0.35 References: In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:fVhasMHi5ZgPLsMYJUxWCekPGi8Gv8ztTpQhKjP9YPNotRal+4p ERNcWb+0SfejVLq02J+D0EDNGCcN9LUdhL9ielOSK2WzG76M22GOCp8wCUJsR4UxDgXBoF+ VodpnhDNIOzWasEA+X+JMe9J0NGtb93w52vscsMoEQ1QOXlaLC0mbqYiOMz7Va4BbDQwkuP MRbPLvAsIjyof4mirkCLA== X-Virus-Checked: Checked by ClamAV on apache.org 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 --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org For additional commands, e-mail: users-help@tomcat.apache.org