Hi all, I'm using activemq in a replicated message store configuration with sequoia (pooled with c3p0). I would like to be able to put a timeout on the queries that activemq uses for persistence because sometimes sequoia can hang a query (i'm working on that issue seperatetly) which causes activemq to hang which causes... This would at least let our app fail fast and possibly recover via some sort of retry or restart of a failed component. Does any one know a way of setting a timeout for the queries that activemq uses to persist messages (ie jdbcStatement.setQueryTimeout). I already have played with the c3p0 timeouts but they only really affect the way the checking out of pooled connections fail etc. I realise this might be complicated when using batched updates but if we could set it when not using that feature it would make it possible to be more reliable.
PS i still think message groups rock! Thanks Dave Cawthorn -- View this message in context: http://www.nabble.com/query-timeout-for-jdbc-persistence-tf4322706s2354.html#a12309538 Sent from the ActiveMQ - User mailing list archive at Nabble.com.
