tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brooke Hedrick <>
Subject Re: [Tomcat JDBC Pool] Close pooled connections via JMX
Date Sun, 04 Mar 2012 15:29:01 GMT
On Mar 4, 2012 5:13 AM, "Chema" <> wrote:
> >>
> >> > That approach doesn't work when the application uses symlinks to get
> >> > data on other Oracle servers.
> Right. With dblinks, it's the RDBMS who opens/closes a session against
> the remote server, via dblinks
> I guess that when you say  "our Oracle database has to be restarted",
> you *only* restart the remote server , right ?

There are cases where either or both get restarted, but the issue is only
when the @otherdb is restarted and not the primary.

> One question :
> do you use any kind of ORM framework ? Some of them (myBatis , for
> example ) allow you to configure different schemas with different
> pingQuery settings.
> So, you could define the remote queries into a particular schema with
> a pingQuery like "SELECT 1 FROM DUAL@REMOTEDB"

We use Spring w/ Hibernate as I recall.  Yes, we have talked about that - a
ping query.  What we don't like about that is now we have a tc ping and app
ping.  We have also discussed just changing the tc borrow/ping to do the
dual@remotedb query as this would test both primary and remote.  We have
tested this and it works.  What stinks about this is we only access the
remotedb 10% of the time.  This means 90% of the time we are making queries
over to the remoted db unnecessarily.

Our solution is a small jmx client we wrote that goes across our 24
machines with about 5 jvms/ machine and 5 datasources/jvm.  It takes a few
seconds to close() those 600 datasources.

> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message