AMQPLib Channel Discovery / Handling Close

I'm looking for a recommended way to deal with unexpected channel closings through this library.

It can be seen from the documentation that an event has occurred, but I'm not entirely clear on how best to detect this event (I know it's simple, but I don't really understand how events are emitted at all, so bear with me), moreover, it's not obvious what I should do about it.

Should I keep track of which subscribers are using this channel and then rewrite them? What are others doing?

What else - isn't there a way to examine the Channel (or ConfirmedChannel) object and determine if everything is "good"? This would be almost preferable for an event-capturing approach, but I can't seem to find a way to do it (well, that's not entirely true). I did something about looking at the "accept" method on the channel to determine if this is bad, but it seems hacky).

Any guidance is greatly appreciated.

+3
node.js node-amqp


source to share


No one has answered this question yet

Check out similar questions:

645
Node.js Best Practice Exception Handling
62
Node.js, Socket.io, Redis pub / sub high volume, low latency difficulties
3
Detecting a video codec in JavaScript
3
Pubsub with Node.js and Socket.io for individual users
2
Node.js: Finding a file opened with fs.createWriteStream () that gets deleted
2
RethinkDB: how to use r.getPoolMaster (). On ("great" with rethinkdb-proxy
1
amqplib nodejs consume rabbit
0
How to set prefetch counter to 1 for amqplib for nodejs
0
AMQPlib nodejs user task parallelism
0
How to check if a channel is alive or not in RabbitMq node-amqplib library?



All Articles
Loading...
X
Show
Funny
Dev
Pics