mattrpav commented on PR #65: URL: https://github.com/apache/activemq/pull/65#issuecomment-1946287847
I really like the idea of improving gc performance and having a per-ActiveMQDestination lock. However, this may break with Composite consumers. 1. consumer-a connects queue://order.1 2. consumer-b connects queue://order.2 3. consumer-c connects queue://order.* 4. consumer-d connects queue://order.1,order.2 I think we could get race conditions where add/delete gets out of order. -- 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]
