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

ASF GitHub Bot commented on ARTEMIS-472:
----------------------------------------

GitHub user jmesnil opened a pull request:

    https://github.com/apache/activemq-artemis/pull/442

    [ARTEMIS-472] add cause to AMQ222137 warning

    JIRA: https://issues.apache.org/jira/browse/ARTEMIS-472

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jmesnil/activemq-artemis 
ARTEMIS-472_AMQ222137_warning

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/442.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #442
    
----
commit c113b910ed3618356cc24c65a0ff3afe80c7e105
Author: Jeff Mesnil <[email protected]>
Date:   2016-04-07T08:16:38Z

    [ARTEMIS-472] add cause to AMQ222137 warning
    
    JIRA: https://issues.apache.org/jira/browse/ARTEMIS-472

----


> AMQ222137 warning does not display the cause of the problem
> -----------------------------------------------------------
>
>                 Key: ARTEMIS-472
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-472
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.2.0
>            Reporter: Jeff Mesnil
>
> While creating a cluster of Artemis servers, I encountered this warning:
> {noformat}
> 18:01:45,009 WARN  [org.apache.activemq.artemis.core.server] (Thread-2 
> (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@491444
> ff-1205056429)) AMQ222137: Unable to announce backup, retrying
> {noformat}
> The cause of the error was not displayed and I had to debug to figure out 
> that I forgot to set the cluster user credentials to let the node join the 
> cluster.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to