[jira] [Resolved] (AMQ-4564) ActiveMQ creates & initializes ACTIVEMQ_LOCK in wrong database when using separate lock data source

["Gary Tully (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-4564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-4564.
-----------------------------

       Resolution: Fixed
    Fix Version/s: 5.9.0

note the new createTablesOnStartup option, which will use the lockerDataSource

> 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
>            Assignee: Gary Tully
>            Priority: Minor
>             Fix For: 5.9.0
>
>         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 was sent by Atlassian JIRA
(v6.1#6144)