Periodically, in an otherwise normal running system, I get one simple
mySQL query/create/update that takes 25+ seconds. I'm pursuing this
with mySQL logs and other steps on the mySQL end. But I have a couple of
questions related to the TC side. I start and end a timer on each side
of a statem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steve,
On 6/4/20 16:59, Sanders, Steve wrote:
> I'm working with an application team that wishes to set the
> timeBetweenEvictionRunsMillis setting of their database connection
> pool to a very low setting - 20ms.
Hah!
Sorry. Continue...
> Accordi
Hi all,
Tomcat Version - 8.5.55
OS - OL7
I'm working with an application team that wishes to set the
timeBetweenEvictionRunsMillis setting of their database connection pool to a
very low setting - 20ms. According to the documentation
(https://tomcat.apache.org/tomcat-8.5-doc/jdbc-pool.html), t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jean-Pierre,
On 7/20/17 6:03 AM, Jean Pierre Urkens wrote:
> I’m running Tomcat-8.-5.15 with following Oracle datasource
> definition:
>
> type="javax.sql.DataSource" username="xxx" password="yyy"
> driverClassName="oracle.jdbc.OracleDriver"
> u
On 20/07/17 11:03, Jean Pierre Urkens wrote:
> Hi All,
>
>
>
> I’m running Tomcat-8.-5.15 with following Oracle datasource definition:
>
> auth="Container" type="javax.sql.DataSource"
>
> username="xxx"
> password="yyy" driverClassN
Hi All,
I'm running Tomcat-8.-5.15 with following Oracle datasource definition:
Tomcat is using the ojdbc6.jar driver library to connect to an Oracle 12c DB
instance. Initially this datasource declaration seems to work fine.
However when resuming a HTTP session after a per
niel Mikusa [mailto:dmik...@vmware.com]
Sent: Wednesday, November 21, 2012 9:11 AM
To: Tomcat Users List
Subject: Re: DB Connection Pool
On Nov 21, 2012, at 9:45 AM, Milan Tomic wrote:
>
>
>> That's a really old version, you should strongly consider upgrading to the
>> l
On Nov 21, 2012, at 9:45 AM, Milan Tomic wrote:
>
>
>> That's a really old version, you should strongly consider upgrading to the
>> latest Tomcat 6.0.x or 7.0.x release.
> My SSO (old JOSSO version) works only with 6.0.18.
>
>> How are you determining this? Are you looking at open connections
> -Original Message-
> From: Milan Tomic [mailto:tomicmi...@yahoo.com]
> Sent: Wednesday, November 21, 2012 4:36 AM
> To: users@tomcat.apache.org
> Subject: DB Connection Pool
>
>
> After 1 month of Tomcat 6.0.18 running, I have 50 opened JDBC
> connections,
> That's a really old version, you should strongly consider upgrading to the
> latest Tomcat 6.0.x or 7.0.x release.
My SSO (old JOSSO version) works only with 6.0.18.
> How are you determining this? Are you looking at open connections from your
> database? Are you looking at JMX stats for th
On Nov 21, 2012, at 5:36 AM, Milan Tomic wrote:
>
> After 1 month of Tomcat 6.0.18 running,
That's a really old version, you should strongly consider upgrading to the
latest Tomcat 6.0.x or 7.0.x release.
> I have 50 opened JDBC connections, which should be closed, but they aren't.
How are yo
in Tomcat 7 (not sure if backported to 6), you configure a
Filip
On 5/11/2011 7:55 AM, Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dale,
On 5/10/2011 7:24 PM, Dale Ogilvie wrote:
The cause of the error was the db admin patching a db package underlying
one use
omcat container db connection
pool?
Hope that helps,
- -chris
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dale,
On 5/10/2011 7:24 PM, Dale Ogilvie wrote:
> The cause of the error was the db admin patching a db package underlying
> one used by our web-app. Post patch all the packages appeared valid to
> the admin, but not to our app using db connections es
Hi,
We just had an issue in production on tomcat 6, a web application was
getting strange errors from the oracle database:
java.sql.SQLException: ORA-06508: PL/SQL: could not find program unit
being called in Package
Our configuration uses a database pool in GlobalNamingResources of
server.xml
15 matches
Mail list logo
