We don't see a lot of traffic on this list about people using PostgreSQL (or other SQL data stores, for that matter), and I've seen it said that there's been less effort spent to test/maintain/improve the JDBC store code, so it's possible that there are bugs that haven't been found yet, and this could be one of those.
Can you tell us more about how you shut down the master? Did you shut down the ActiveMQ instance itself, or just pull the plug on the server, or...? And did the slave never successfully start, or just not for some short amount of time? The JDBC locker ( http://activemq.apache.org/pluggable-storage-lockers.html) has a lockKeepAlive period; is it possible that you stopped letting the slave try to reconnect before that period had elapsed? Tim On Sun, Aug 7, 2016 at 10:15 PM, davidyce <ye...@ncs.com.sg> wrote: > Hi, > > We have a problem when we shut down serverA (hosting amq master), server B > (hosting amq slave) did not run as Master. In the end, amq becomes > blocked. > No incoming, no outgoing messages. Our initial investigation is due to the > amq slave not able to acquire the database lock which amq master is still > holding on. > > OS: Centos 7 > Activemq version:5.9.0 > Postgre database:9.5.3 > amq master:61616 > amq slave:61617 > > Appreciate any help. > > Thanks in advance. > > > > -- > View this message in context: http://activemq.2283324.n4. > nabble.com/Postgresql-Database-Lock-Issue-in-Master- > Slave-setup-tp4715112.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. >
