-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel,
On 4/4/12 8:46 AM, Daniel Mikusa wrote:
- Original Message -
My db connections seem to be lost after an extended period of
inactivity (for a web application). And the only way to get the
connections to work again is to restart
I'm using tomcat 7, in a spring mvc application. The properties is in my
spring-context.xml file.
bean id=dataSource class=org.apache.tomcat.jdbc.pool.DataSource
destroy-method=close
property name=driverClassName value=com.mysql.jdbc.Driver/
property name=url
Daniel,
Your suggestion seems to have worked so far, thanks!
testOnBorrow=true and validationQuery=SELECT 1
On Wed, Apr 4, 2012 at 8:46 AM, Daniel Mikusa dmik...@vmware.com wrote:
- Original Message -
My db connections seem to be lost after an extended period of
inactivity
On 04/04/2012 12:08, S Ahmed wrote:
My db connections seem to be lost after an extended period of inactivity
(for a web application). And the only way to get the connections to work
again is to restart tomcat.
My tomcat.jdbc.pool.Datasource settings have:
property name=maxActive
- Original Message -
My db connections seem to be lost after an extended period of
inactivity
There could be a number of reasons that this occurs. Perhaps a network issue
is causing them to be disconnected or the database may be timing them out. At
any rate, it's not likely that
timeBetweenEvictionRunsMillis=-1
minEvictableIdleTimeMillis=28800
-Original Message-
From: Daniel Mikusa [mailto:dmik...@vmware.com]
Sent: Wednesday, April 04, 2012 7:46 AM
To: Tomcat Users List
Subject: Re: jdbc pool properties
- Original Message -
My db connections seem to be lost after an extended
L Propes barry.l.pro...@citi.com
To: Tomcat Users List users@tomcat.apache.org
Sent: Wednesday, April 4, 2012 7:53:26 AM
Subject: RE: jdbc pool properties
There are some databases that do go in and periodically kill off
connections, aside from the Tomcat settings.
In addition
password=
roles=admin-gui,admin-script,manager-gui,manager-script,manager-jmx,manager-status/
Any ideas?
Thanks in advance,
Jonathan
--
View this message in context:
http://tomcat.10.n6.nabble.com/What-is-the-best-way-to-view-Tomcat-JDBC-pool-properties-in-Tomcat-7-tp4557182p4558028.html
Sent
ideas?
Thanks in advance,
Jonathan
--
View this message in context: http://tomcat.10.n6.nabble.**
com/What-is-the-best-way-to-**view-Tomcat-JDBC-pool-**
properties-in-Tomcat-7-**tp4557182p4558028.htmlhttp://tomcat.10.n6.nabble.com/What-is-the-best-way-to-view-Tomcat-JDBC-pool-properties
-status/
user username= password=
roles=admin-gui,admin-script,manager-gui,manager-script,manager-jmx,manager-status/
Any ideas?
Thanks in advance,
Jonathan
--
View this message in context:
http://tomcat.10.n6.nabble.com/What-is-the-best-way-to-view-Tomcat-JDBC-pool-properties
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan,
On 3/8/12 6:29 AM, hodgesz wrote:
Yes you are correct we are creating the pool in Spring
configuration as it is more natural for our application, but the
only problem we see now is once we upgraded to 7.0.26 we see the
following
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan,
So, ConnectionPool.getProxyConstructor definitely makes a decision
about what interfaces to expose when generating a proxy for a
PooledConnection (sorry for the word-wrapping):
public Constructor? getProxyConstructor(boolean xa) throws
so that doesn't seem like
the solution here.
-Jonathan
--
View this message in context:
http://tomcat.10.n6.nabble.com/What-is-the-best-way-to-view-Tomcat-JDBC-pool-properties-in-Tomcat-7-tp4557182p4558561.html
Sent from the Tomcat - User mailing list archive at Nabble.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan,
On 3/8/12 10:19 AM, hodgesz wrote:
Well the exact same Spring code doesn't throw an exception with
6.0.29 version of Tomcat.
See Rainer's note in the bug you filed: those properties didn't exist
in 6.0.x.
I have already entered a bug
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jonathan,
On 3/8/12 10:19 AM, hodgesz wrote:
Well the exact same Spring code doesn't throw an exception with
6.0.29 version of Tomcat.
See Rainer's note in the bug you filed: those properties didn't exist
in 6.0.x.
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
André,
On 3/8/12 11:34 AM, André Warnier wrote:
Christopher Schultz wrote:
It looks like the MBean (or maybe the pool itself) is exposing
something that shouldn't be treated as a property: the
connection itself. Calling getConnection (or, in
Thanks guys. I will file a new bug with the details you provided about it
exposing too many get methods.
--
View this message in context:
http://tomcat.10.n6.nabble.com/What-is-the-best-way-to-view-Tomcat-JDBC-pool-properties-in-Tomcat-7-tp4557182p4559731.html
Sent from the Tomcat - User
In 6.0.29 we used the Spring MBeanExporter to export the Tomcat JDBC pool
properties.
We are still able to view them with this approach in JConsole and using the
JMXProxy Servlet with Tomcat 7.
However since Tomcat JDBC pool is part of Tomcat 7 are its properties
exposed without using
On 8 Mar 2012, at 02:26, hodgesz hodg...@gmail.com wrote:
In 6.0.29 we used the Spring MBeanExporter to export the Tomcat JDBC pool
properties.
We are still able to view them with this approach in JConsole and using the
JMXProxy Servlet with Tomcat 7.
However since Tomcat JDBC pool is part
19 matches
Mail list logo
