Publication error event not sent when RabbitMQ is not up

Hello,

I’m having trouble with RabbitMQ and error management. Here’s how to reproduce:

1. Run container RabbitMQ
2. Run my application with broker connect
3. Shutdown RabbitMQ
4. Trigger the function that send a message to RabbitMQ

Here is my code that is triggered:

async myFunc() {
  try {
    const publication = await this.broker.publish("toto", msg);
    publication
      .on("error", (err, messageId) => {
        console.error("Publisher error", err, messageId);
      })
      .on("success", messagesId => {
        console.log("success", messagesId);
      });
  } catch (error) {
      console.error("Catch error", error);
  }
}

Unfortunately, my console.error("Publisher error", err, messageId); is never executed. But somewhere else I have broker.on("error", console.error); just after the connect, and my error is logged here.

My problem is I’d like to know there’s an error when I’m executing my “myFunc” function. This function is executed in a API and I’d like to trace the error back to the user when RabbitMQ is inaccessible. Or even better, maybe there is a way to find the connection status for a vhost?

Thanks!

[cressie176]

Publications

I’ve added a paused event and abort method as described above

Broker Events

I’ve added vhost_initialised (although you still can’t get this during startup - it’s for reconnections only)

I’ve also added the vhost details to broker.error events

broker.on('error', (err, { vhost, connectionUrl }) => {
  // ...
});

Published as rascal@9.4.0

[AnthonySendra]

OK, get it. Your example looks great to me. If I have both pause event and abort function, I’ll be able to do what I want!