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: domain of hilavalensia@gmail.com
 designates 209.85.216.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type;
        b=LgJbum0YdiHUwyJs8xue+wCwnfiG8gXu4t4KxH/8qYlVj0vtwR7l2cpmiIQLxwf7nM
         H0guWTlUNrdO4Rm1EQY3H/x8oCR3VlpmqhHOdd5qgREm9pp4WWv6cKI7kX367YCTDljs
         rJ+QCFu+tzflOX+RLCoUOI5xQPh8W/Mgr+Pwk=
MIME-Version: 1.0
In-Reply-To: <4D77E350.2030901@ice-sa.com>
References: <4D6FBF27.50103@hanik.com>
 <201103041059.42461.nsushkin@openfinance.com>
 <AANLkTi=jFPmfnuaHsY8CNgQWH=WAh=DcbC-9-vY79+Zi@mail.gmail.com>
 <201103061259.26698.nsushkin@openfinance.com>
 <AANLkTinqexXc6jxtLDE96S7ubqjy9xsYgMj4vO7t_7dL@mail.gmail.com>
 <AANLkTik9DfbxQz2wyJN2c6_WVa6RNWq78Luz3G44sqvb@mail.gmail.com>
 <il2bom$3j1$2@dough.gmane.org>
 <AANLkTinYOeVjxEyotBBPyp_v8vdfvXbNMukGdpYPyoKV@mail.gmail.com>
 <AANLkTimHvUN9G5yxjLjWhiiaqXyA+0XHGshOAB77YY6z@mail.gmail.com>
 <4D74B818.40503@apache.org> <4D74FC5A.4090406@hanik.com>
 <AANLkTik0ewZ6GCTvHqHWn0f2DDcvOgRsmSuCN09QszyU@mail.gmail.com>
 <AANLkTim9u=5eYw+QJDjmH+m9RJda014-Ojpm6-Csfc0W@mail.gmail.com>
 <AANLkTikKH0GdMLSSirGm+0VjkypVCzg1oKXiTKz1XLDJ@mail.gmail.com>
 <AANLkTimS0AWAomkkT3vjow+FZgjkOpHMMyQW79rMXnm4@mail.gmail.com>
 <4D77BA2A.60503@hanik.com>
 <AANLkTiksR36+_v1EFMu1Fb6aOzdFefGMAumOKki8aMGp@mail.gmail.com>
 <4D77E350.2030901@ice-sa.com>
From: =?UTF-8?B?15TXmdec15Q=?= <hilavalensia@gmail.com>
Date: Wed, 9 Mar 2011 22:33:43 +0200
Message-ID: <AANLkTimAxByGPKJ+_J5BXN7t7wpRAMjpL+D_-Y9S_xBU@mail.gmail.com>
Subject: Re: Cleaning up after tomcat jdbc-pool?
To: Tomcat Users List <users@tomcat.apache.org>
Content-Type: multipart/alternative; boundary=bcaec51ba31748700e049e12a657

--bcaec51ba31748700e049e12a657
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Sure, when I'll have a final results and see that the leak is no longer
exist (prays the lord :P) I'll post a final thread with the solution :]


2011/3/9 Andr=C3=A9 Warnier <aw@ice-sa.com>

> =D7=94=D7=99=D7=9C=D7=94 wrote:
>
>> I'll define it. thanks :]
>> I've implemented 2 changes in production servers - one with the new pool
>> (and still jtds drivers) and one with new pool + switching to jdbc
>> drivers.
>> both has windows authentication enabled.
>> the servers look pretty stable until now, but I'm waiting to see the
>> memory
>> behaviour in the next few days. on servers with the jtds driver, basic
>> pool
>> and windows authentication, the leak appeared pretty fast, so I'm
>> expecting
>> results real soon.
>> I'll keep you posted.
>> Thanks you guys, you've been a great help so far :]
>> Hila
>>
>>  So, if I understand this correctly, this also terminates the other
> thread, now with a subject "Tomcat NTLM Authentication", right ?
>
> Meaning that the MS JDBC driver works, it does NTLM authentication, and
> does not have a memory leak ?
> If so, you may want to post a final message to the other thread, so that
> people following that one would know how it ends, and what the solution w=
as.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>

--bcaec51ba31748700e049e12a657--