[rabbitmq-discuss] publishing messages causes messages to stop being collected
dtenenba at fhcrc.org
Mon Feb 7 19:09:48 GMT 2011
On Mon, Feb 7, 2011 at 9:43 AM, Marek Majkowski <majek04 at gmail.com> wrote:
> On Wed, Feb 2, 2011 at 21:37, Dan Tenenbaum <dtenenba at fhcrc.org> wrote:
> > All 3 steps were working, then I added another instance of a1 on another
> > machine and step 3 stopped working. Neither instance of a1 receives any
> > messages. rabbitmqctl tells me they are piling up in the queue, and a2
> > also tell me step 2 is still happening.
> > Specifically, the action that caused step 3 to fail was not simply adding
> > another instance of a1 but having that instance do step 1.
> > Hope someone can tell me what is going on here. a1 is a web app and the
> > first instance of it is on my local machine, and a2 represents me trying
> > deploy this app in a production environment.
> I'm afraid I can't help. Your code looks sane, and I don't know
> amqp at node enough to spot any client problems.
> Did you managed to find problem yourself?
Not really. I ended up doing a really hacky workaround where I created a
different exchange for each node.js client and published the messages on the
appropriate exchange. This is not really satisfactory, though, because
ultimately I want to add new consumers for these messages and would like
them to only have to deal with one exchange.
Oh, and instead of this:
> Hope someone can tell me what is going on here. a1 is a web app and the
> first instance of it is on my local machine, and a2 represents me trying
> deploy this app in a production environment.
...i meant to say:
a1 is a web app, and the first instance of it is on my local machine; the
second is me trying to deploy this app in a production environment.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss