It seems that only using the new jdbc pool has solved the memory leak :] it's funny that the idea to use it came from a different thread here in the users list. :] Thanks for your help Hila
בתאריך 9 במרס 2011 22:33, מאת הילה <hilavalen...@gmail.com>: > 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é Warnier <a...@ice-sa.com> > >> הילה 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 was. >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >>
