You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/07/23 21:10:57 UTC
[jira] [Closed] (AMQ-4564) ActiveMQ creates & initializes
ACTIVEMQ_LOCK in wrong database when using separate lock data source
[ https://issues.apache.org/jira/browse/AMQ-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQ-4564.
-----------------------------
Resolution: Incomplete
No test case provided to reproduce this error.
> ActiveMQ creates & initializes ACTIVEMQ_LOCK in wrong database when using separate lock data source
> ---------------------------------------------------------------------------------------------------
>
> Key: AMQ-4564
> URL: https://issues.apache.org/jira/browse/AMQ-4564
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.5.1
> Reporter: Tim Boemker
> Priority: Minor
> Attachments: activemq.log, broker-config.xml
>
>
> When configured to use a secondary database for locking, ActiveMQ creates and initializes ACTIVEMQ_LOCK in the primary database. It then starts as slave because it can't lock the table in the secondary database.
> Workaround: manually copy the ACTIVEMQ_LOCK table from the primary database to the secondary database.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira