activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dillon (JIRA)" <j...@apache.org>
Subject [jira] Closed: (AMQ-703) Bad example on MasterSlave page
Date Tue, 02 May 2006 18:13:37 GMT
     [ https://issues.apache.org/activemq/browse/AMQ-703?page=all ]
     
Jason Dillon closed AMQ-703:
----------------------------

    Resolution: Fixed

I just updated the wiki page.

> Bad example on MasterSlave page
> -------------------------------
>
>          Key: AMQ-703
>          URL: https://issues.apache.org/activemq/browse/AMQ-703
>      Project: ActiveMQ
>         Type: Improvement

>   Components: Documentation
>     Reporter: Jason Dillon
>     Priority: Critical

>
>
> This page http://activemq.org/MasterSlave lists an example of:
> {noformat}
> Configuring MasterSlave
> A master broker doesn't need any special configuration - it's a normal broker until a
slave broker attaches itself.
> To identify a broker as a slave - there is just one property to set (see below) and an
option - so configuration is nice and easy:
> <broker masterConnectURI="tcp://masterhost:62001" shutdownOnMasterFailure="false">
. . . </broker>
> {noformat}
> But the name of the property is *NOT* masterConnectURI, it is masterConnectionURI, which
in the table below is corrected.
> The "nice and easy" example should be updated.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message