OK, we figured it out. Someone was using the connection to
monitoring. This monitoring took 24 hits every 3 seconds across
all of our websites.
Thx for your assistance.
--- Norris Shelton <[EMAIL PROTECTED]> wrote:
> Sorry, I forgot to specify the version.
>
> TC 4.1.12
>
> --- Norris Shel
I would like to, but we are not "allowed" to use pooling yet.
--- Seth Ladd <[EMAIL PROTECTED]> wrote:
> Norris Shelton wrote:
> > We have the manager app for each of our contexts set-up to
> use
> > the DB to authenticate users. Unfortunately, it is using
> TONS
> > of connections. Over an 8 mi
Sorry, I forgot to specify the version.
TC 4.1.12
--- Norris Shelton <[EMAIL PROTECTED]> wrote:
> We have the manager app for each of our contexts set-up to use
> the DB to authenticate users. Unfortunately, it is using TONS
> of connections. Over an 8 min period, it used 1200
> connections.
Norris Shelton wrote:
We have the manager app for each of our contexts set-up to use
the DB to authenticate users. Unfortunately, it is using TONS
of connections. Over an 8 min period, it used 1200 connections.
We have 2 boxes, each with 16 contexts with their own manager
context. Here is what
May be you should try using a DataSourceRealm, so that connections
could be pooled by DBCP.
On Thu, 18 Nov 2004 11:05:02 -0800 (PST), Norris Shelton
<[EMAIL PROTECTED]> wrote:
> We have the manager app for each of our contexts set-up to use
> the DB to authenticate users. Unfortunately, it is us
We have the manager app for each of our contexts set-up to use
the DB to authenticate users. Unfortunately, it is using TONS
of connections. Over an 8 min period, it used 1200 connections.
We have 2 boxes, each with 16 contexts with their own manager
context. Here is what the manager context of
