loom-dev Digest, Vol 53, Issue 36

[Arkadiusz Gasiński]

> The incubator module containing StructuredTaskScope (structured
> concurrency) and extent locals has
> not yet been integrated, and so these features are not available in JDK 19
> EA.

Moving on, how will updates to the structured concurrency JEP be published?
Will you continue to publish loom builds?

Also, how far off are we from integrating the SC JEP into the mainline?
Tbh, I'm a bit surprised that SC did not make it as a preview feature in
19 together with virtual threads, but I can imagine that the latter was far
more important, and most/all efforts were put there to make sure it's ready
for 19.

Anyways, shall we expect significant changes to the SC API, or is it mature
enough and only minor changes will be made?

Thanks,
Arek

On Sat, May 14, 2022 at 1:55 PM <loom-dev-request at openjdk.java.net> wrote:

> Send loom-dev mailing list submissions to
>         loom-dev at openjdk.java.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://mail.openjdk.java.net/mailman/listinfo/loom-dev
> or, via email, send a message with subject or body 'help' to
>         loom-dev-request at openjdk.java.net
>
> You can reach the person managing the list at
>         loom-dev-owner at openjdk.java.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of loom-dev digest..."
>
>
> Today's Topics:
>
>    1. Re: Virtual threads in JDK 19 EA builds (Pedro Lamar?o)
>    2. -Djdk.tracePinnedThreads (Cay Horstmann)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 13 May 2022 10:47:50 -0300
> From: Pedro Lamar?o <pedro.lamarao at prodist.com.br>
> To: Ron Pressler <ron.pressler at oracle.com>
> Cc: loom-dev <loom-dev at openjdk.java.net>
> Subject: Re: Virtual threads in JDK 19 EA builds
> Message-ID:
>         <CAC8PkgH4iC2BAXWB0GwmbNSQrpojX+Q57x_R0P8ZvU=
> LnepwJA at mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
>
> Thanks for this notice! Yesterday I checked the "release notes" on the
> early access build page and it did not include this information. I assumed
> Loom had not yet been integrated.
>
> Em sex., 13 de mai. de 2022 ?s 06:19, Ron Pressler <
> ron.pressler at oracle.com>
> escreveu:
>
> > Hi.
> >
> > Last weekend we integrated JEP 425 (virtual threads preview) [1] into the
> > mainline JDK.
> > Starting with JDK 19 build 22, available now, the Early Access builds of
> > JDK 19 over at jdk.java.net
> > include virtual threads.
> >
> > The incubator module containing StructuredTaskScope (structured
> > concurrency) and extent locals has
> > not yet been integrated, and so these features are not available in JDK
> 19
> > EA.
> >
> > Now would be a good time to start experimenting with virtual threads and
> > report any issues you find
> > (to this mailing list, or directly to JBS if you have an account) prior
> to
> > JDK 19?s GA release in September.
> > This would help us improve virtual threads in JDK 19.
> >
> > Please give it a try: https://jdk.java.net/19/
> >
> > ? Ron
> >
> > [1]: https://openjdk.java.net/jeps/425
> >
> >
> >
>
> --
> Pedro Lamar?o
> https://www.prodist.com.br
> Securing Critical Systems
> Tel: +55 11 4380-6585
>
> Antes de imprimir esta mensagem e seus anexos, certifique-se que seja
> realmente necess?rio.
> Proteger o meio ambiente ? nosso dever.
> Before printing this e-mail or attachments, be sure it is necessary.
> It is in our hands to protect the environment.
>
>
> ------------------------------
>
> Message: 2
> Date: Fri, 13 May 2022 19:41:39 +0200
> From: Cay Horstmann <cay.horstmann at gmail.com>
> To: loom-dev <loom-dev at openjdk.java.net>
> Subject: -Djdk.tracePinnedThreads
> Message-ID: <cb77f5ba-6a31-b91d-ce3d-59a5870da011 at gmail.com>
> Content-Type: text/plain; charset=UTF-8; format=flowed
>
> I re-read the section on the jdk.tracePinnedThreads sysprop in
> https://openjdk.java.net/jeps/425:
>
> "The system property jdk.tracePinnedThreads triggers a stack trace when
> a thread blocks while pinned."
>
> I interpreted this to expect a stack trace whenever a thread blocks
> while pinned.
>
> Since that's not been my experience, I ran a simple program that spawned
> ten virtual threads, each acquiring the same monitor. With
> -Djdk.tracePinnedThreads=full, I got one stack trace and not ten. Of
> course, one is enough, so I guessed this is by design. And then I
> discovered java.lang.PinnedThreadPrinter.
>
> It might be good to clarify the JEP. "Recently seen duplicates are not
> printed."
>
> Cheers,
>
> Cay
>
> --
>
> Cay S. Horstmann | http://horstmann.com | mailto:cay at horstmann.com
>
>
> End of loom-dev Digest, Vol 53, Issue 36
> ****************************************
>