I’m facing a problem where the consumer internal D...
# generalj
Jack Pham
11/05/2025, 11:11 PMI’m facing a problem where the consumer internal DLQ producer can’t connect due to a conflict with another producer with the same name. This issue was fixed in version 4.1.0, but it requires Java 17, which is not feasible for us at the moment (still with java8 ) I want to implement a short-term workaround to detect this issue and recreate the consumer with a different name, which, in theory, should resolve the conflict. The pulsar client implementation, however, seems to hide the entire DLQ handling, with exceptions not thrown or propagated back to external code. Is there a way to archive what I need here?
l
Lari Hotari
11/06/2025, 8:14 AMAre you referring to https://github.com/apache/pulsar/pull/23577 ? That's included in maintenance releases as well. For example commit https://github.com/apache/pulsar/commit/7e70df27 is included in branch-4.0 since 4.0.1 release.
Lari Hotari
11/06/2025, 8:19 AMThere's also PIP-409 https://github.com/apache/pulsar/blob/master/pip/pip-409.md included since 4.0.4 release which allows customization of DLQ and RetryLQ producer configuration such as setting producer name explicitly.
j
Jack Pham
11/06/2025, 6:10 PMthanks, this is much better than what i was about to do.