[#MB-1038] document use of ioExceptionHandler and useDatabaseLock="false" to re-establish DB connection after DB restart in single broker instance deployment

FUSE Message Broker

document use of ioExceptionHandler and useDatabaseLock="false" to re-establish DB connection after DB restart in single broker instance deployment

Created: 07/Dec/11 11:20 AM Updated: 03/Apr/13 03:53 PM

Component/s:

documentation

Affects Version/s:

5.5.1-fuse-01-11

Fix Version/s:

None

Environment:

all

Issue Links:

Linked

This issue is linked from:

~~MB-827~~ Message broker won't come back when the databse goes offline and comes back online

Description

« Hide

In a single broker instance deployment with the default configuration, the broker will stop if the connection to Database is lost. The instance will need to be restarted when the DB is back on line. A configuration update is required if you want the broker instance to remain running and reestablish the connection when database is back on line.

The configuration update is mentioned here https://issues.apache.org/jira/browse/AMQ-1780?focusedCommentId=13016295&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13016295
and here https://issues.apache.org/jira/browse/AMQ-1780?focusedCommentId=13016295&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13016295.

NOTE: In a master/slave instance deployment, this configuration will not work. (see ~~MB-827~~)

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Gary Tully added a comment - 20/Jun/12 03:15 PM

The JDBC case is now handled correctly by the LeaseLocker, ripe for doco: see http://fusesource.com/issues/browse/MB-1156