Hi gordon. This is an option I considered, but I am actually looking to bind the host instead of port because I am running this on a PaaS. So basically it would need to be useable by more than one person on one machine. They would spin up an app, and add a qpid broker to it. The PaaS allocates different ip's for applications which exist as CNAME aliases on the host node. So app name qpid may exist on node: "node1" as qpid with an IP of 127.1.34.2 (random ip) and would need to bind to that IP. The apps are in linux containers. So I know there is a possibility here. I was desperately looking through the qpid documentation to see if there's a way to do this on the java end.
Greatly appreciate the help, though. Kyle On 12/19/13 5:04 PM, "Gordon Sim" <g...@redhat.com> wrote: >On 12/19/2013 09:03 PM, Kyle Crumpton (kcrumpto) wrote: >> Hi Ted. I am using version 0.22. I actually got qpid from tar: >> qpid-java-broker-0.22.tar.gz > >Sorry, my mistake! I should have realised from the 8080 port. > >I'm not sure about setting the interface, but one other way around the >problem you described is to specify different ports for each of the >broker instances. > >E.g. qpid-server -prop "qpid.amqp_port=10000" -prop >"qpid.http_port=10001" -prop "qpid.rmi_port=10002" -prop >"qpid.jmx_port=10003" -prop "qpid.work_dir=/path/to/broker1" > >then > >qpid-server -prop "qpid.amqp_port=11000" -prop "qpid.http_port=11001" >-prop "qpid.rmi_port=11002" -prop "qpid.jmx_port=11003" -prop >"qpid.work_dir=/path/to/broker2" > >etc > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org >For additional commands, e-mail: dev-h...@qpid.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
