RobertIndie commented on issue #403: URL: https://github.com/apache/pulsar-client-go/issues/403#issuecomment-2146368018
> For our Java services the message is automagically redelivered after a fixed delay to (one of the shared) existing consumers regardless of consumer connection/reconnection. Maybe I get your points. Are you setting the AckTimeout of the Java consumer to a non-zero value(The default value is 0)? The java consumer will redelivery the messages after it can't ack the messages within the `ackTimeout`. This timeout is managed by the client-side code, not by the broker. However, the broker handles the redelivery logic, allowing it to resend messages to another consumer if necessary. For the Go client, there is no AckTimeout configuration. Instead, message redelivery should be handled using either the NackBackoffPolicy or DLQPolicy. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
