Unhandled 'error' event

[duartemadueno]

Unhandled 'error' event

[squaremo]

Are you using only rabbit.js? This error probably means testNODE has been declared from elsewhere, e.g., by using the Node AMQP client directly at some point. rabbit.js more or less assumes that won't be the case; i.e., that it has free range to declare what it likes (all AMQP programs have to assume this, in practice).

[duartemadueno]

Yes, i'm only using rabbit.js. I know why the error is being thrown but would like to handle that specific exception so i can return a custom message to the client.

The solution was:

• process.on('uncaughtException', function (err) {});

Anyway, this isn't the best solution, as you might see.

[squaremo]

Ah I see. It's quite tricky to handle AMQP errors, since any error tends to invalidate the AMQP channel, meaning you have to construct a new one and start things again. But you are right that rabbit.js could probably do a lot better than let exceptions be unhandled all the way up.

[duartemadueno]

Since this is just a small project there's no problem working things this way but, it's true, would really handy if we could handle AMQP errors through rabbit.js

Another thing, hope you guys don't mind but i changed socket.js file so it can receive a RoutingKey on write. In my case, i don't know which RoutingKeys will be used by the client.

[squaremo]

@duartemadueno master branch now has error reporting on sockets; basically, if an AMQP channel reports an error, any socket using it will emit an error and close. If you've not moved on from rabbit.js, would you try it out to see if it works like you'd expect? Extra test cases very welcome. Thanks!

[duartemadueno]

Hi @squaremo right now i'm using https://github.com/postwait/node-amqp and that solved my problem. Sorry i can't help you on this particular issue

[squaremo]

No worries! I understand -- it's more flexible using node-amqp directly, if a bit more work too.
Thanks for pointing out the problem in the first place.