tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Hall <rfha...@yahoo.com>
Subject Re: [Tomcat JDBC Pool] Close pooled connections via JMX
Date Sun, 04 Mar 2012 20:49:38 GMT




________________________________
From: Brooke Hedrick <brooke.t.hedrick@gmail.com>
To: Tomcat Users List <users@tomcat.apache.org> 
Sent: Sunday, March 4, 2012 12:21 PM

> On Mar 4, 2012, at 1:35 PM, Chema <demablogia@gmail.com> wrote:
> 
>>> 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.
>> 
>> Well, I don't know how works Hibernate , but I know that you can have
>> many SessionFactory
>> Can you define different SessionFactory with different settings , for
>> example, with different pingQuery value?
>> Does Hibernate have a pingQuery setting ?
>>
> 
> Even if it does, are we actually losing the close() method for the connection pool mbean? 
If so, why?
> 
> This change would mean requiring many development teams to change many apps.  I don't
see the value of requiring that change - if it is actually the case we are losing the close()
method.


Have you tried defining views in the primary database based on the @otherdb queries?

- Bob

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


Mime
View raw message