jvmdc opened a new issue, #22505:
URL: https://github.com/apache/pulsar/issues/22505

   ### Search before asking
   
   - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) 
and found nothing similar.
   
   
   ### Motivation
   
   The error messages the server emits in 
https://github.com/apache/pulsar/blob/master/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/AbstractTopic.java
 do not contain the topic name. 
   
   Both the Java client and the .NET client simply use these error messages 
without adding any additional context, making it harder to understand what is 
going on as the end-user.
   
   ### Solution
   
   Adding the topic to the error messages would aid in debugging issues as a 
end-user:
   | Current                                                 | Proposed         
                                                   |
   
|---------------------------------------------------------|---------------------------------------------------------------------|
   | Producer with name 'Test' is already connected to topic | Producer with 
name 'Test' is already connected to topic 'SomeTopic' |
   | Topic reached max same address producers limit          | Topic 
'SomeTopic' reached max same address producers limit          |
   | Topic reached max producers limit                       | Topic 
'SomeTopic' reached max producers limit                       |
   
   
   ### Alternatives
   
   Alternatively the clients should refrain from simply forwarding the error 
messages but add the additional context instead. In this case, it becomes up to 
each client on how to phrase the errors and may provide a less uniform 
experience across Pulsar clients.
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] I'm willing to submit a PR!


-- 
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]

Reply via email to