Error: channel is not available

I’m creating an API which will accept the message and then will publish it to the queue.

So i have initialized my app.module.ts

@Module({
  imports: [
     RabbitMQModule.forRootAsync(RabbitMQModule, {
      imports: [ConfigModule],
      inject: [ConfigService],
      useFactory: (configService: ConfigService) => ({
        uri: configService.get('RABBIT_MQ_URI')
      })
    }),
  ],
  controllers: [AppController],
  providers: [
    AppService
  ],
})
export class AppModule {}

And in the service imported the library AMQPService like this constructor(private readonly amqpConnection: AmqpConnection){}

So when, using the methods exposed like this this.amqpConnection.channel.assertExchange(exchange.name, exchange.type, exchange.options); and it throws Error: channel is not available.

When logged amqpConnection, recieved this object

AmqpConnection {
  messageSubject: Subject {
    closed: false,
    currentObservers: null,
    observers: [],
    isStopped: false,
    hasError: false,
    thrownError: null
  },
  logger: Logger { context: 'AmqpConnection', options: {} },
  initialized: Subject {
    closed: false,
    currentObservers: null,
    observers: [],
    isStopped: false,
    hasError: false,
    thrownError: null
  },
  _managedChannels: {},
  _channels: {},
  config: {
    prefetchCount: 10,
    defaultExchangeType: 'topic',
    defaultRpcErrorBehavior: 'REQUEUE',
    defaultSubscribeErrorBehavior: 'REQUEUE',
    exchanges: [],
    defaultRpcTimeout: 10000,
    connectionInitOptions: { wait: true, timeout: 5000, reject: true },
    connectionManagerOptions: {},
    registerHandlers: true,
    enableDirectReplyTo: true,
    channels: {},
    enableControllerDiscovery: false
  }
}

Expectations:

• Should be able to assert an exchange.

[nitoba]

I think this is bug of the version 2.3.0 In version “@golevelup/nestjs-rabbitmq”: “2.2.0” all works fine

[fmalk]

Since we’re still using 2.2 for our backend, best if we tried to update it to current version and see if problem persist. However that’s not a priority. When that happens, I’ll report back here.