log4js-node / log4js-node/rabbitmq

how-to DEBUG mode investigate connection issues

Open
#5 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
8
Forks
4
PR merge metrics
No merged PRs in 30d

Description

Migrating from native "amqplib": "^0.5.2" to log4js.
Getting error on the connection socket.
We have ssl enabled and process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";

```
ERR { Error: Socket closed abruptly during opening handshake
ERR at Socket.endWhileOpening (/app/node_modules/amqplib/lib/connection.js:260:17)
ERR at Socket.emit (events.js:203:15)
ERR at endReadableNT (_stream_readable.js:1129:12)
ERR at process._tickCallback (internal/process/next_tick.js:63:19)
```

the config.rabbit is:
```
var rabbit = {
type: '@log4js-node/rabbitmq',
host: '127.0.0.1',
port: 5672,
username: 'guest',
password: 'guest',
routing_key: 's.system.log',
exchange: 's.exchange.infrastructure.logger',
mq_type: 'topic',
con: {heartbeat: 30, protocol: 'amqps'}
}````

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the RabbitMQ configuration and the amqplib stack trace at node_modules/amqplib/lib/connection.js:260. Reproduce the SSL connection attempt using the shown host, port, and protocol, then trace the opening-handshake failure and document the configuration or connection change that resolves it.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js, rabbitmq
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.