-
Notifications
You must be signed in to change notification settings - Fork 81
Open
Description
Hi,
I encountered the following Error that was not handled and Node exited due to this error. Not sure if I can catch the error to prevent Node from exiting ?
Rhea : 3.0.1
Nodejs: 20.12.2
Error: SMF AD bind response error
at Receiver.link.on_detach (/workspace/node_modules/rhea/lib/link.js:165:86)
at Session.on_detach (/workspace/node_modules/rhea/lib/session.js:745:27)
at Connection.<computed> [as on_detach] (/workspace/node_modules/rhea/lib/connection.js:855:30)
at c.dispatch (/workspace/node_modules/rhea/lib/types.js:946:33)
at Transport.read (/workspace/node_modules/rhea/lib/transport.js:117:36)
at Connection.input (/workspace/node_modules/rhea/lib/connection.js:567:37)
at TLSSocket.emit (node:events:513:28)
at TLSSocket.emit (node:domain:489:12)
at addChunk (node:internal/streams/readable:315:12)
at readableAddChunk (node:internal/streams/readable:289:9)
const newContainer = container.create_container();
var connection = newContainer.connect({
host: XXX,
port: XXX,
transport: "tls",
key: certificate.key,
cert: certificate.cert,
reconnect: true,
idle_time_out: 1000 * 70,
});
connection.on("message", async function (context) {
// Handling new messages
});
connection.on("connection_close", (context) => {
console.log(`Connection close`, context);
});
connection.on("disconnected", () => {
console.log("Bus receiver connection receives disconnected");
});
connection.on("connection_error", (reason) => {
console.log(
"Bus receiver connection receives connection error",
reason.error,
reason
);
});
Is there a way to prevent the app from exiting ? Do you have an idea where this error is originating ?
Thanks
Metadata
Metadata
Assignees
Labels
No labels