On 26/08/14 17:50, Rob Godfrey wrote:
Doh - yeah - that was my fault... fixed now I hope,
-- Rob
Just updated, seems to be behaving now, I also got
node recv.js amqp://guest:guest@localhost:5673/amq.fanout
node send.js -a amqp://guest:guest@localhost:5673/amq.fanout
working so the JavaScript/WebSocket send and recv behave the same as the
C ones
more little victories, thanks!
Getting the qpid-config.js might be a bit of effort to figure out what's
playing up. I changed the connection URL in the QMF plugin to:
"connectionURL" :
"amqp://guest:guest@/localhost?brokerlist='tcp://0.0.0.0:5672'",
and used the same connectionURL in the QMF GUI and that seems to be
playing nicely with the QMF plugin bound to the "localhost" vhost
but qpid-config.js is currently just hanging :-(
Or rather on the plus side it *is* sending messages to
vhost:localhost/qmf.default.direct and it is creating a subscription
queue on the localhost vhost too, I'll need to dig a bit further to see
what's breaking - I can't see a binding for the subscription queue, but
that might just be because it should be bound to the localhost vhost's
default direct exchange which won't show up in the bindings.
today has made me sad, so I'll probably sleep on it.
Frase
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
