If you use c3p0 as a connection pooler, then you can run a slave which will
retry to obtain the lock on the lock table. Then when the database is
restarted, or goes down, the master goes down, and the slave broker will
take over when the database comes back up. You'll then need something to
rest
Do the comments on https://issues.apache.org/activemq/browse/AMQ-2498 help
at all?
On 21 April 2010 09:07, lernit2007 wrote:
>
> I use the last activemq release version.
>
>
> lernit2007 wrote:
> >
> > Hello,
> >
> > if my jdbc-database is restarted or goes down, then the broker goes down
> > to
I use the last activemq release version.
lernit2007 wrote:
>
> Hello,
>
> if my jdbc-database is restarted or goes down, then the broker goes down
> too. It is possible to say that the broker always try to connect to the
> database or how can I solve this problem. Thanks im behaviour.
>
--
Can you create a jira and attach the full log, a checkpoint failure should
not force a broker shutdown, that is, that stack trace should not. There
should be something else in the logs I think.
do the validationQuery and testOnBorrow on the pool really take effect?
Seems odd that connection refuse
Hi Dejan,
I am using ActiveMQ 5.3.
Thanks,
PG
--
View this message in context:
http://old.nabble.com/Broker-goes-down-when-database-is-restarted-tp26327953p26338023.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
what version are you using?
Cheers
--
Dejan Bosanac - http://twitter.com/dejanb
Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net
On Thu, Nov 12, 2009 at 11:47 PM, au.pg wrote:
>
> Hi,
>
> When I database
