Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Mon, 3 Jun 2013 20:58:21 +0000 (UTC)
From: "Tim Boemker (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: <JIRA.12650338.1370006742710.59339.1370293101286@arcas>
In-Reply-To: <JIRA.12650338.1370006742710@arcas>
References: <JIRA.12650338.1370006742710@arcas>
Subject: [jira] [Commented] (AMQ-4564) ActiveMQ creates & initializes
 ACTIVEMQ_LOCK in wrong database when using separate lock data source
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/AMQ-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13673550#comment-13673550 ] 

Tim Boemker commented on AMQ-4564:
----------------------------------

I can't say for sure, and my test environment is shared, so I'm not able to test with 5.8.0 now.
                
> 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