qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rob Godfrey (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Resolved: (QPID-22) Provide run scripts for clustered broker
Date Wed, 12 Dec 2007 10:15:43 GMT

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

Rob Godfrey resolved QPID-22.

       Resolution: Won't Fix
    Fix Version/s:     (was: M3)

Will not be fixed - cluster code removed until new clustering solution

> Provide run scripts for clustered broker
> ----------------------------------------
>                 Key: QPID-22
>                 URL: https://issues.apache.org/jira/browse/QPID-22
>             Project: Qpid
>          Issue Type: New Feature
>          Components: Java Broker
>    Affects Versions: M1, M2
>         Environment: Unix, Linux, WIndows, Cygwin
>            Reporter: Marnie McCormack
> Note that this task relates to existing java broker clustering capability.
> We currently have qpid-server (which uses qpid-run) and qpid-server.bat which make it
painless for users to start up the broker, having installed qpid on their host. These scripts
take care of classpath, configuration defaulting etc.
> For starting a clustered broker we don't have an equivalent, though I think qpid-run
could probably be called without changes for unix/linux, qpid-clustered-server and qpid-clustered-server.bat
scripts. These scripts which would simply use the class org.apache.qpid.server.cluster.Main
and handle the -j flag which specifies the lead broker in the cluster to be joined.
> For example, if a user wishes to start a three broker cluster s/he can start the first
clustered broker without specifying the -j flag. This broker will then act as the lead broker
in the cluster. The user then starts the second and third brokers, specifying the -j option
with the host:port of the lead broker to identify the cluster to join.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message