[
https://issues.apache.org/jira/browse/QPID-4444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13500573#comment-13500573
]
Robbie Gemmell commented on QPID-4444:
--------------------------------------
Are you using one of the 0.18, 0.20 alpha (beta should be getting cut now, the
initial release branch creation happened an hour ago), or trunk broker? It is
enabled and configured on port 8080 by default on all of these. Does your
broker log file contain any errors? (You can change the port if need be by
adding a <port> .. </port> sub-element to the management.http element shown
above).
The output you got when directing your browser to the AMQP port (5672) is
simply the broker responding as required with a supported AMQP protocol version
after receiving an unsupported (HTTP in this case) protocol version
initiatation.
> QPID Broker fails when running qpid-config command
> --------------------------------------------------
>
> Key: QPID-4444
> URL: https://issues.apache.org/jira/browse/QPID-4444
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.19
> Environment: linux
> Reporter: Andrew Burks
> Labels: newbie
>
> I have checked out the updated source code (up to revision 1411028) and when
> executing "qpid-config -a guest/guest@protoqpid:5672", I receive the error
> "Failed: RuntimeError: Timed out waiting for broker to synchronize".
> Note: protoqpid is just an alias to localhost
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
