alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed
URL:
https://github.com/apache/pulsar-client-node/issues/78#issuecomment-604658303
@yosiat thank you!!
This is an automated message from the
alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed
URL:
https://github.com/apache/pulsar-client-node/issues/78#issuecomment-602643477
> Changing my code to, instead of `console.log(`Sent message: ${msg}`);` to
`console.log(`Sent message: ${msg} - client
alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed
URL:
https://github.com/apache/pulsar-client-node/issues/78#issuecomment-601179535
This is a playground example though. In a real system you can't necessarily
control the rate of messages produced, as they
alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed
URL:
https://github.com/apache/pulsar-client-node/issues/78#issuecomment-598421709
@equanz your example handles the rejection, sure. But there shouldn't be a
rejection in the first place. A producer closing
alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed
URL:
https://github.com/apache/pulsar-client-node/issues/78#issuecomment-595671568
That would be hard to tell without looking at the code. We know the client
uses a connection pool for the original client
alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed
URL:
https://github.com/apache/pulsar-client-node/issues/78#issuecomment-595336522
I tried 2.4 of the client as it was the one recommended by Kafkaesque, but
the problem was still there for me. Didn't bother
alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed
URL:
https://github.com/apache/pulsar-client-node/issues/78#issuecomment-595136257
@alijmlzd did you try rolling back to an older version? Any luck finding one?
alexyans commented on issue #78: Error: Failed to send message: AlreadyClosed
URL:
https://github.com/apache/pulsar-client-node/issues/78#issuecomment-595133166
I have the same problem. Sending a message immediately after initializing
the producer works fine, so it can't be a TLS
