I'm using tomcat 7, in a spring mvc application. The properties is in my
spring-context.xml file.
On Fri, Apr 6, 2012 at 2:09 PM, Christopher Schultz <
ch...@christopherschultz.n
-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 res
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 wrote:
>
>
> - Original Message -
> > My db connections seem to be lost after an extended period of
> > inactivity
>
> There cou
> From: "Barry L Propes"
> To: "Tomcat Users List"
> 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.
>
> I
"true"
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 d
- 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
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:
>
>
>
>
>
ConnectionHandler.**
>> process(AbstractProtocol.java:**579)
>> at
>> org.apache.tomcat.util.net.**JIoEndpoint$SocketProcessor.**
>> run(JIoEndpoint.java:307)
>> at
>> java.util.concurrent.**ThreadPoolExecutor$Worker.**
>> runTask(ThreadPool
little more detail we have enabled all the new Manager roles while
we test this issue.
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
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
-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,
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 h
-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
n't need it now 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 l
-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
N
-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 exce
-pool-properties-in-Tomcat-7-tp4557182p4558028.html
Sent from the Tomcat - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h
On 8 Mar 2012, at 02:26, hodgesz 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 p
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 the
19 matches
Mail list logo
