Hi Rob, Sorry for the really late reply / hope you remember this thread.
I got some assistance from the irc. I pulled the latest source using svn
checkout http://svn.apache.org/repos/asf/qpid/trunk/qpid qpid
Then I ran patch -i QPID-5437.patch --dry-run -p0 in the Java branch.
The patch seemed
So, when I'm developing I normally just start up the broker with
build/bin/qpid-server
from the qpid/java root.
From there you can either configure the IP through the config file or using
the web UI for the server. The difference is that the HTTP port should now
allow binding address as an
Hi Rob,
Thank you a bunch I'm going to give this a try.
On 12/19/13 6:11 PM, Rob Godfrey rob.j.godf...@gmail.com wrote:
I've created https://issues.apache.org/jira/browse/QPID-5437 and attached
a
quick patch to allow for HTTP ports to be bound to a speicifc address in
the same way that AMQP
I am just curious if there is a way to bind qpid to an IP such as 127.1.244.129
The reason I ask is I'm looking to deploy many instances to a PaaS and will
need multiple running instances. This is not possible if everything tries to
bind to localhost:8080.
Does anyone know of a way to
On 12/19/2013 06:45 PM, Kyle Crumpton (kcrumpto) wrote:
I am just curious if there is a way to bind qpid to an IP such as 127.1.244.129
The reason I ask is I'm looking to deploy many instances to a PaaS and will
need multiple running instances. This is not possible if everything tries to
Hi. I did this and I got the error: Unrecognized option: --interface
On 12/19/13 12:59 PM, Gordon Sim g...@redhat.com wrote:
On 12/19/2013 06:45 PM, Kyle Crumpton (kcrumpto) wrote:
I am just curious if there is a way to bind qpid to an IP such as
127.1.244.129
The reason I ask is I'm looking
Kyle,
That feature was added in release 0.20
(https://issues.apache.org/jira/browse/QPID-3351). You may be using an
older version.
-Ted
On 12/19/2013 03:15 PM, Kyle Crumpton (kcrumpto) wrote:
Hi. I did this and I got the error: Unrecognized option: --interface
On 12/19/13 12:59 PM,
Hi Ted. I am using version 0.22. I actually got qpid from tar:
qpid-java-broker-0.22.tar.gz
On 12/19/13 3:00 PM, Ted Ross tr...@redhat.com wrote:
Kyle,
That feature was added in release 0.20
(https://issues.apache.org/jira/browse/QPID-3351). You may be using an
older version.
-Ted
On
Sorry Kyle,
Gordon and I are giving you information about the C++ broker, not the
Java broker. I will need to defer to one of the Java broker folks to
answer for that component.
-Ted
On 12/19/2013 04:03 PM, Kyle Crumpton (kcrumpto) wrote:
Hi Ted. I am using version 0.22. I actually got
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
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
Hi Kyle,
the Java Broker uses a number of different ports, depending on which
plugins are enabled. If I remember correctly there are some ports which
can be bound to only certain interfaces, but others (HTTP and JMX
management) which we cannot so restrict. As well as port conflicts you are
going
Hello Kyle,
Yes, this is supported. You can make the AMQP port bind to a
particular interface using the binding address attribute. Use the
Web Management Console to edit the AMQP port and specify a binding
address (127.1.244.129 in your case). Once done, restart the Broker
for that change
It is not currently possible to specify an interface for the Java brokers
HTTP ports to bind (though it could be made possible...), it is only
possible to specify the port number currently. It does not bind just
localhost, it will listen on all interfaces.
Same for the JMX ports (though with the
Hi Keith, Rob.
Thank you for your replies.
I am actually at a point where I am trying to get qpid running on a PaaS
instance in a linux container.
Scenario is
User creates app: test in namespace test
domain is example.com
so you create this app on your PaaS which exists on your server:
So it looks like it will be a completely trivial fix to allow the HTTP port
to bind to different interfaces... the JMX (as Robbie says) not so much...
however if you don't need the JMX management plugin you can disable it.
If we patch up the HTTP management then all you'll need to do is change
On 19 December 2013 23:36, Rob Godfrey rob.j.godf...@gmail.com wrote:
So it looks like it will be a completely trivial fix to allow the HTTP port
to bind to different interfaces... the JMX (as Robbie says) not so much...
however if you don't need the JMX management plugin you can disable it.
I've created https://issues.apache.org/jira/browse/QPID-5437 and attached a
quick patch to allow for HTTP ports to be bound to a speicifc address in
the same way that AMQP ports are. The patch is against the head of trunk
rather than 0.22, though I don't imagine it'd be too difficult to get it to
18 matches
Mail list logo
