[
https://issues.apache.org/jira/browse/AMQ-9394?focusedWorklogId=932385&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-932385
]
ASF GitHub Bot logged work on AMQ-9394:
---------------------------------------
Author: ASF GitHub Bot
Created on: 29/Aug/24 12:06
Start Date: 29/Aug/24 12:06
Worklog Time Spent: 10m
Work Description: 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.
Issue Time Tracking
-------------------
Worklog Id: (was: 932385)
Time Spent: 2h 10m (was: 2h)
> Tech Preview: Virtual Thread support
> ------------------------------------
>
> Key: AMQ-9394
> URL: https://issues.apache.org/jira/browse/AMQ-9394
> Project: ActiveMQ Classic
> Issue Type: New Feature
> Reporter: Matt Pavlovich
> Assignee: Matt Pavlovich
> Priority: Major
> Labels: #virtualthread
> Fix For: 6.2.0
>
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> Initial technical preview of Virtual Thread support
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
