Database locks and ActiveMQ

If you are using a database with your ActiveMQ installation, you may want to set useDatabaseLock to “false” in the journaledJDBC element of your configuration. This is there so that you can have a master/slave configuration and the instance that can lock a specific table gets to be the master. If you only have one server, this doesn’t do you any good. Also, databases like PostgreSQL which use vacuum can have issues with these long-running transactions.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s