[
https://issues.apache.org/jira/browse/CAMEL-15657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17210095#comment-17210095
]
Claus Ibsen commented on CAMEL-15657:
-------------------------------------
Lets look at whether we use any synchronized (lock) { } or synchronized methods
that may be affected. First priority is around runtime routing of messages via
the routing engine.
The bootstrap with initializating Camel is not a problem as there is a single
thread doing this work.
Old collection classes like Vector or Hashtable is not in use.
> JDK biased locking to be removed in Java 17
> -------------------------------------------
>
> Key: CAMEL-15657
> URL: https://issues.apache.org/jira/browse/CAMEL-15657
> Project: Camel
> Issue Type: Task
> Components: camel-core
> Reporter: Claus Ibsen
> Priority: Major
> Fix For: 3.x
>
>
> jdk15 initiated the process of removing *biased locking* from the JVM as
> per JEP 374 (https://openjdk.java.net/jeps/374). That release switched
> the default setting from enabled to disabled. The plan is to see if any
> users squeal and, if not, proceed to remove it in jdk16 or jdk17.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
