cshannon commented on PR #1172:
URL: https://github.com/apache/activemq/pull/1172#issuecomment-2317462596

   If testing shows there are issues with performance/pinning (and I'm sure 
there are) we may want to wait to release this as experimental or not, it would 
defeat the purpose of releasing it. Or at the very least have a big warning etc.
   
   I personally don't think we should go around and just start messing with 
replacing a bunch of synchronized blocks just because of this. While we do need 
to fix the locking and synchronization in the broker, that is a major effort 
and needs to be well planned and is non-trival and not something that would 
likely happen in a 6.x release as it would be nice to modernize things for 7.x. 
And because there's a fix coming in the JDK (hopefully with the 25 LTS release) 
we could just wait for that. 
   
   Other projects like Caffeine are 
[waiting](https://github.com/ben-manes/caffeine/issues/1468) for the fix as 
well. 
   


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


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact


Reply via email to