AMQP settings are too global
Reported by Ben Hood | April 21st, 2011 @ 03:46 PM
I've just ran into a problem when running the agent using jetty:run and overwriting the config to match the config used on a live site. The issue is that the config I posted contained references to a different AMQP host than the one that agent is configured to connect to (by default this is localhost). So for example, if you have post a config like this:
<endpoint name="fooApp"
url="amqp://some.other.host//queues/foo"
content-type="application/json"
inbound-url="amqp://some.other.host//queues/bar"
inbound-content-type="application/Transaction+json">
then the participant will get wired to the localhost broker, and not the broker on some.other.host.
Probably what should happen is that we don't configure a default AMQP host, rather we always spin up connections based on the Endpoint config.
No comments found
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
A Real Time Differencing Tool.