On 12 May 2016 9:00 am, "Igor Cicimov" wrote:
>
>
> On 12 May 2016 12:16 am, "Niranjan Babu Bommu"
wrote:
> >
> > I tried the same config on test stacks. numidle always "10" why it is
> > behaving differently in prod?
> >
> Are you sure your testing db config is identical to the prod one?
>
> >
On 12 May 2016 12:16 am, "Niranjan Babu Bommu"
wrote:
>
> I tried the same config on test stacks. numidle always "10" why it is
> behaving differently in prod?
>
Are you sure your testing db config is identical to the prod one?
>auth="Container"
> type="javax.sql.DataSource"
I'm re-posting my ds
On Wed, May 11, 2016 at 10:16 AM, Niranjan Babu Bommu <
niranjan.bo...@gmail.com> wrote:
> I tried the same config on test stacks. numidle always "10" why it is
> behaving differently in prod?
>
>auth="Container"
> type="javax.sql.DataSource"
>
I tried the same config on test stacks. numidle always "10" why it is
behaving differently in prod?
On Wed, May 11, 2016 at 7:35 AM, Niranjan Babu Bommu <
niranjan.bo...@gmail.com> wrote:
> Hi Mark
> I have included defined data source in this mail, do you want me to
> include complete server.x
Hi Mark
I have included defined data source in this mail, do you want me to include
complete server.xml?
thanks
Niranjan
On Wed, May 11, 2016 at 7:19 AM, Mark Thomas wrote:
> On 11/05/2016 11:58, Niranjan Babu Bommu wrote:
> > Hi,
> >
> > we are migrating prod servers to tomcat, since we are do
On 11/05/2016 11:58, Niranjan Babu Bommu wrote:
> Hi,
>
> we are migrating prod servers to tomcat, since we are doing it slowly we
> have found an issue in jdbc connection pool, tomcat is not releasing idle
> jdbc connections, even we have tried setting maxIdle="10" but "NumIdle 97"
> always. due
Hi,
we are migrating prod servers to tomcat, since we are doing it slowly we
have found an issue in jdbc connection pool, tomcat is not releasing idle
jdbc connections, even we have tried setting maxIdle="10" but "NumIdle 97"
always. due to this threads are piling up in database.
I'm including my
