Curious, isn’t this the same issue with ANY native method call? Why does this need special treatment - it is easily worked around by using a worker pool in user level code if it’s a common operation. 

On Sep 20, 2025, at 9:09 AM, Yuval Lombard <[email protected]> wrote:


Hey Peter,

I am sorry for the lack of proper context. Yes! this is the issue


On Sat, 20 Sept 2025 at 18:06, Peter Eastham <[email protected]> wrote:
Hey Yuval,

I'll leave it to others in the group for a proper answer, but I think I can say it would be useful to include the exact issue. I did a look through JBS and found this one about virtual thread parking with InetAddress. Is that what you're talking about?

Thanks,
- Peter

On Sat, Sep 20, 2025 at 8:25 AM Yuval Lombard <[email protected]> wrote:
Hello team,

Is there an estimated time/jdk release for fixing the InetAddress isReachable issue?

--

Kind regards,

Yuval Lombard

Staff Software Engineer

+972.50.548.0111

[email protected]

<logo_black.png>



--

Kind regards,

Yuval Lombard

Staff Software Engineer

+972.50.548.0111

[email protected]

<logo_black.png>

Reply via email to