-
Bug
-
Resolution: Answered
-
Highest
-
None
-
6.0.0
-
24
-
Severity 2 - Major
-
831
-
This problem is caused by a bug in the Java runtime: JDK-8214418 HttpClient falls in running with 100% cpu usage after an error signalled on channel (Backported as JDK-8241054)
The fix has been verified to be available in AdoptOpenJDK 11.0.8 - https://github.com/AdoptOpenJDK/openjdk-jdk11u/commit/8d1b63a4db2c6348a97b3cf45bd4d2caa7cad6b5
Webhooks are likely impacted by the same problem as is described here: https://jira.atlassian.com/browse/BSERV-11796
In fixing BSERV-11796, all that was done was to disable TLSv1.3 in the HTTP Client, however that client instance is specific to the repository importer.
The above is suspected to relate to the following JDK bug:
- JDK-8214418 HttpClient falls in running with 100% cpu usage after an error signalled on channel
Workaround
1) Run Bitbucket Server with Java 8; or
2) (Not yet verified) The issue is observed with Java 11 that uses TLS v1.3. It is likely that TLS v1.2 works fine and will not cause this issue. This can be done by setting the following JVM parameter: -Dhttps.protocols=TLSv1.2 while starting bitbucket server up.
- is incorporated by
-
BSERV-12374 Java 11 TLS 1.3 problems
- Closed
- is related to
-
JRASERVER-70780 Webhooks intermittently stop working with Java 11
- Closed
- was cloned as
-
BSERV-12180 Code search intermittently stops working with Java 11 JRE
- Closed