> -Original Message-
> From: Madan KN [mailto:madan...@gmail.com]
> Sent: Monday, April 08, 2013 9:29 AM
> To: Tomcat Users List
> Subject: Re: Tomcat JDBC Pooling - Connections
>
> # 99% percent of the time we do have need for 200 active sessions
> across our appl
Hi:
But I can see that you aren't using Tomcat JDBC pool, but oracle.jdbc.pool.
OracleDataSource , right ?
And I don't know how you set up your datasource to more than 200 maxActive
connections
Indeed, I don't know how you define the size of connection pool
Regards
2013/4/8 Madan KN
> # 9
On Apr 8, 2013, at 10:28 AM, Madan KN wrote:
> # 99% percent of the time we do have need for 200 active sessions across
> our application cluster. But due to some high spikes we end up with 2000
> sessions which is ending up in the pool with out getting evicted.*
>
> *
> # I think once the applic
# 99% percent of the time we do have need for 200 active sessions across
our application cluster. But due to some high spikes we end up with 2000
sessions which is ending up in the pool with out getting evicted.*
*
# I think once the application is out of peak the connections are returned
in eithe
On Apr 8, 2013, at 3:23 AM, Madan KN wrote:
> *Hi All,*
>
> Currently we are using tomcat jdbc pooling for oracle 11g R12.
What version of Tomcat are you using? If you are using the pool directly
outside of Tomcat, what version of it are you using?
> The problem
> we are facing is during the
*Hi All,*
Currently we are using tomcat jdbc pooling for oracle 11g R12. The problem
we are facing is during the peak traffic (less than %2) of time the
connections spike up to more than 100 sessions & never comes back to the
normal / desired pool size. Due to the connections are returned either i
