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
> close connections that ran out of memory.
>
Look at the "maxAge" property in
http://people.apache.org/~fhanik/jdbc-pool/jdbc-pool.html
it is created just to deal with the database sessions that have memory
leaks, and the leak is somewhat predictable timing wise
best
Filip
> Don't know if such a scenario has been tested. I am curious to hear.
>
> On Mar 7, 2011 10:46 AM, "הילה"<hilavalensia@gmail.com> wrote:
>
> 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<devlists@hanik.com>
>
>
>
>> On 3/7/2011 3:48 AM, Mark Thomas wrote:
>>
>>
>>> On 07/03/2011 10:39, הילה wrote:
>>>
>>>
>>>> I found this...
>>>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
|