makeomatic / makeomatic/ms-socket.io-adapter-amqp
Console log error: "when replying to message response could not be delivered"
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I have started using ms-socket.io-adapter-amqp as a replacement for socket.io-amqp. Everything seems working fine except many console log as below in every minute.
{"level":20,"time":1652718540702,"pid":19,"hostname":"api-develop-6888c64ffd-84mqf","name":"amqp","msg":"{\"error\":null}","msg":"when replying to message response could not be delivered"}
My configuration:
var app = require('../app'); // expressjs app instance
var io = require('socket.io')(server, {
pingTimeout: 60000,
transports: ['websocket'],
});
// hard coded RABBIT_CONNECTION for local environment development. The value will be configured with an Amazon MQ connection string
process.env.RABBIT_CONNECTION = "amqp://192.168.56.1";
process.env.ADAPTER_QUEUE_PREFIX = "LOCALHOST-ADAPTER"
if (process.env.RABBIT_CONNECTION && process.env.ADAPTER_QUEUE_PREFIX) {
const {
ConnectionString
} = require('connection-string');
const {
AdapterFactory
} = require('ms-socket.io-adapter-amqp')
const conn = new ConnectionString(process.env.RABBIT_CONNECTION);
const adapter = AdapterFactory.fromOptions({
connection: {
host: conn.hostname,
port: conn.port,
login: conn.user,
password: conn.password,
ssl: conn.protocol === 'amqps'
},
exchange: `${process.env.ADAPTER_QUEUE_PREFIX}-socket.io`
});
io.adapter(adapter);
}
app.set('socketio', io);
app.io = io;
Libraries versions:
"ms-socket.io-adapter-amqp": "^9.0.1",
"socket.io": "^4.5.0",
Could you please take a look ?
Thank you very much!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is identified in the issue. Start by reproducing the recurring message with the shown Socket.IO 4.5.0 and ms-socket.io-adapter-amqp 9.0.1 configuration, then trace the adapter's AMQP response-delivery logging. Done means the cause of the undelivered replies is identified and the recurring error is resolved or clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, rabbitmq, typescript
- 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