My experience using loom for a load generator

[Alan Bateman]

On 25/06/2020 15:21, eric.ackermann at student.hpi.de wrote:
> :
> I re-ran the tests with the refreshed builds without -XX:-UseContinuationChunks and did not observe any JVM crashes any more.
> However, I encountered an internal error in ReentrantLock.java I thought you might be interested in, see the stack trace below [1].
> The problem seems to occur when instances of AsyncHttpClient are created inside a virtual thread while other instances are sending requests in other virtual threads, and I was not able to reliably reproduce it.
> I am not sure whether this is a bug in Loom or async-http-client, but since I never experienced this issue on JVMs 11 through 13 when using Kotlin coroutines I am convinced that my application and Kotlin are not the culprits.
> I am currently using version 2.10.4 of async-http-client, Kotlin version 1.3.70 and Windows 10 1903 (Build 18362.900).
>
Thanks for the mail.  Would you mind trying to run with the following 
options:

    -XX:+UnlockDiagnosticVMOptions -XX:DisableIntrinsic=_currentThread

This disables some recently introduced code and I'm curious if it makes 
this exception go away.

-Alan