At first we only use the default jdbcPersistenceAdapter (without the lease
lock) -> not surviving a network disconnection
Then we tried to change the wrapper.conf to restart the AMQ service -> not
working also
wrapper.filter.trigger.1=Failed to start Apache ActiveMQ
wrapper.filter.action.1=RESTART
Hello Tim,
We finally get through this issue using the below AMQ lease database locker
configuration.
Now AMQ service survive network disconnection and auto-reconnection from/to
AMQ & database.
Thank you for your help.
--
View this message in context:
http://activemq.2283324.n4.nabbl
-> ok
However, when AMQ1 network back again, AMQ1 service never come back online
-> ?
Is there any specific configuration to apply to keep the AMQ service running
on network disconnection or AMQ service back online automatically after the
network re-connection ?
Thanks for your help,
