cast it to java.sql.Connection
On 3/8/2012 4: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 exception in the logs when
We can't cast it since it isn't our code. The MBeanDumper class is part of
Tomcat JMXProxy.
On Sat, Mar 10, 2012 at 1:43 PM, Filip Hanik - Dev Lists devli...@hanik.com
wrote:
cast it to java.sql.Connection
On 3/8/2012 4:29 AM, hodgesz wrote:
Yes you are correct we are creating the pool
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 exception in the logs when viewing
through JMXProxy. The data is retrieved correctly so the exception
-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
Well the exact same Spring code doesn't throw an exception with 6.0.29
version of Tomcat.
I have already entered a bug
https://issues.apache.org/bugzilla/show_bug.cgi?id=52842 for similar
exceptions thrown with version 7 that didn't exist in 6.
I didn't use XA previously and I don't need it now
-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 the
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
12 matches
Mail list logo
