entvex commented on issue #274: URL: https://github.com/apache/pulsar-dotpulsar/issues/274#issuecomment-3273748230
It looks like you're encountering the error: The error “Producer with name 'xxxxx' is already connected to topic 'yyyyy'” means there is already an active producer with that exact name on that topic, so the broker rejects the new connection. Pulsar allows multiple producers per topic, but if you explicitly set a producerName, it must be unique per topic. For partitioned topics, the client creates one producer per partition, and name uniqueness is enforced per partition, so the same collision occurs at the partition level. In your JMeter setup with 10 threads and a loop count of 500, it’s likely that multiple threads are trying to create producers with the same name at the same time, or a previous producer wasn’t closed cleanly and is still considered active by the broker for a short period. To resolve this, try to generate unique names yourself (for example, by appending a UUID or thread identifier). Reuse a single producer per thread or workload where possible, and make sure producers are closed properly, allowing time for the broker to register the disconnect after failures. You also left a lot of fields black. Please include DotPulsar version .NET runtime version OS and architecture A minimal code snippet showing how you're managing producers Any relevant JMeter configuration details -- 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]
