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
On 03/07/2011 06:46 PM, Nicholas Sushkin wrote:
I don't think the default pool has any glaring leaks. However, your db may.
I have ran into cases when Oracle would run out of PGA memory, which cleared
with tomcat restart.
It may help to use connection validation feature of tomcat's new pool to
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
הילה 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
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
On 3/7/2011 8:00 AM, הילה wrote:
How do I know if I use the new pool?
just by specifying the
org.apache.tomcat.jdbc.pool.DataSourceFactory
AFAICT yes.
what is the advantages of using the new pool?
in which cases should I use it?
See http://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.html
So it's only for use on Tomcat 7?
I have installed tomcat 6.0.29
2011/3/7 Olivier Lefevre lefev...@yahoo.com
On 3/7/2011 8:00 AM, הילה wrote:
How do I know if I use the new pool?
just by specifying the
org.apache.tomcat.jdbc.pool.DataSourceFactory
AFAICT yes.
what is the advantages
I found this
http://people.apache.org/~fhanik/tomcat/jdbc-pool.html
that I see that it suits for tomcat 6 as well
but I can't find tomcat-jdbc.jar for download, and I understood I need it to
use the new pool.
from where can I download it?
Thanks
Hila
בתאריך 7 במרס 2011 12:28, מאת הילה
On 07/03/2011 10:39, הילה wrote:
I found this
http://people.apache.org/~fhanik/tomcat/jdbc-pool.html
that I see that it suits for tomcat 6 as well
but I can't find tomcat-jdbc.jar for download, and I understood I need it to
use the new pool.
from where can I download it?
There is no
On 3/7/2011 3:48 AM, Mark Thomas wrote:
On 07/03/2011 10:39, הילה wrote:
I found this
http://people.apache.org/~fhanik/tomcat/jdbc-pool.html
that I see that it suits for tomcat 6 as well
but I can't find tomcat-jdbc.jar for download, and I understood I need it to
use the new pool.
from where
Thanks :]
Let's see if it'll somewhat help with the memory leak, or with memory
management at all
2011/3/7 Filip Hanik - Dev Lists devli...@hanik.com
On 3/7/2011 3:48 AM, Mark Thomas wrote:
On 07/03/2011 10:39, הילה wrote:
I found this
I don't think the default pool has any glaring leaks. However, your db may.
I have ran into cases when Oracle would run out of PGA memory, which cleared
with tomcat restart.
It may help to use connection validation feature of tomcat's new pool to
close connections that ran out of memory.
Don't
On Sunday, March 06, 2011 07:45:19 הילה wrote:
Hey,
i'd glad to get you help with something :]
I tried to put
org.apache.tomcat.jdbc.pool.DataSourceFactory
but after restarting tomcat, i get the error
could not load resource factory class
why is that?
how can I define my application to
How do I know if I use the new pool?
just by specifying the
org.apache.tomcat.jdbc.pool.DataSourceFactory
?
what is the advantages of using the new pool?
in which cases should I use it?
Thanks :)
2011/3/6 Nicholas Sushkin nsush...@openfinance.com
On Sunday, March 06, 2011 07:45:19
On Thursday, March 03, 2011 19:24:11 Olivier Lefevre wrote:
Can we see the relevant part of your context.xml, too?
Sure. It's something like:
?xml version=1.0 encoding=UTF-8?
Context antiJARLocking=true path=@deploy.path@
Resource auth=Container
Thanks! But this:
factory=org.apache.tomcat.jdbc.pool.DataSourceFactory
is the default, I believe. Didn't you say you were using something else?
-- O.L.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For
On 03/04/2011 02:04 PM, Olivier Lefevre wrote:
Thanks! But this:
factory=org.apache.tomcat.jdbc.pool.DataSourceFactory
is the default, I believe. Didn't you say you were using something else?
is not the default. org.apache.tomcat.dbcp.dbcp.BasicDataSourceFactory
is default
Filip
-- O.L.
hi Nicholas,
where is your pool configured? In server.xml or in your application context?
If it is configured in server.xml, then this is a bug, the thread should have
been created with the class loader from the pool itself.
If it is configured in the application context, then this simply means
On 3/3/2011 11:44 AM, Olivier Lefevre wrote:
On 3/3/2011 5:17 PM, Filip Hanik - Dev Lists wrote:
If it is configured in the application context, then this simply means
you forgot to call DataSource.close on the connection pool when your
web application is stopped.
This is confusing advice
Hi, Filip,
My tomcat jdbc pool is configured in my app's context.xml. My app uses MyBatis
3 to do the work. I store MyBatis SqlSessionFactory in ServletContext
attributes.
I was able to get DataSources back from Batis SqlSessionFactory, and invoke
.close on each. The leak seems to have gone
Can we see the relevant part of your context.xml, too?
Thanks,
-- O.L.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Hi, Filip,
Is there a recommended way to clean up after the pool? I am getting the
following error message and I wonder if I need to add some code to prevent
memory leak.
2011-03-02 22:20:20,786 ERROR [http-8081-1]
org.apache.catalina.loader.WebappClassLoader - The web application [/…]
22 matches
Mail list logo
