You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"[BrokerPool] Failed to connect to seed broker, trying another broker from the list: Connection error: Client network socket disconnected before secure TLS connection was established"
#1658
Open
EmmanDizon opened this issue
Jan 15, 2024
· 0 comments
I do not encountered any error when I produce message one time only. But when I executed the producer in loop, I consistently encountering this error "[BrokerPool] Failed to connect to seed broker, trying another broker from the list: Connection error: Client network socket disconnected before secure TLS connection was established"
Another catch, when i try to remove the producer.disconnect (when running in loop), I'm no longer encounter any error, this is consistent, not just intermittent (meaning not a connection issue)
Here is the code for better understanding ->
Here is the calling of producer in array:
async sendEventMessage() {
const iterations = Array.from({ length: 3 });
for (const _ of iterations) {
const message = // any message here
await this.#kafka.produceEvent(message);
}
}
I do not encountered any error when I produce message one time only. But when I executed the producer in loop, I consistently encountering this error "[BrokerPool] Failed to connect to seed broker, trying another broker from the list: Connection error: Client network socket disconnected before secure TLS connection was established"
Another catch, when i try to remove the producer.disconnect (when running in loop), I'm no longer encounter any error, this is consistent, not just intermittent (meaning not a connection issue)
Here is the code for better understanding ->
Here is the calling of producer in array:
Here is the producer:
Here is the calling of
async sendEventMessage
:Summary:
OS: Windows 10
KafkaJS:
"kafkajs": "^2.2.3",
"kafkajs-snappy": "^1.1.0",
Node version: v18.17.1
running the execution in lambda
The text was updated successfully, but these errors were encountered: