From: Alan Bateman
Sent: Sunday, June 8, 2025 10:52 PM
To: Shruthi . ; net-dev@openjdk.org
Cc: Syed Moinudeen ; SREENIVAS MAKINEEDI
Subject: [EXTERNAL] Re: Suggestion needed to port the fix to JDK17 and JDK11S
On 31/05/2025 20: 12, Shruthi . wrote: Hi Alan, I wanted to follow up on
On 31/05/2025 20:12, Shruthi . wrote:
Hi Alan,
I wanted to follow up on the update I shared earlier
I’ve successfully backported the preClose re-order changes to *JDK
17* and ran the |Race.java| test case *500 times*. It passed
consistently without any failures. For validation, I also ran the
; net-dev@openjdk.org
Cc: Syed Moinudeen ; SREENIVAS MAKINEEDI
Subject: Re: [EXTERNAL] Re: Suggestion needed to port the fix to JDK17 and
JDK11S
Hi Alan,
I was able to successfully build the OpenJDK headstream with the preClose
reordering patch, which you have shared:
pending_signals.patch
@openjdk.org
Cc: Syed Moinudeen ; SREENIVAS MAKINEEDI
Subject: Re: [EXTERNAL] Re: Suggestion needed to port the fix to JDK17 and
JDK11S
Hi Alan,
I was able to successfully build the OpenJDK headstream with the preClose
reordering patch, which you have shared:
pending_signals.patch<ht
: Syed Moinudeen ; SREENIVAS MAKINEEDI
Subject: [EXTERNAL] Re: Suggestion needed to port the fix to JDK17 and JDK11S
On 14/03/2025 09: 22, Shruthi . wrote: The issue which we are seeing is not
reproducible in JDK21 or higher version Okay, so you might be chasing a
different issue? For the JDK then ma
the fix to JDK17 and JDK11S
On 14/03/2025 06: 16, Shruthi . wrote: Thanks Alan. I’ll port the patch you
attached. It’s not a clean port to JDK 17, partly because UnixDispatcher. java
is missing. I’m making the necessary changes manually. Once the build is ready,
I’ll validate
On 14/03/2025
Sent: Wednesday, March 12, 2025 9:15 PM
To: Shruthi . ; net-dev@openjdk.org
Cc: Syed Moinudeen ; SREENIVAS MAKINEEDI
Subject: [EXTERNAL] Re: Suggestion needed to port the fix to JDK17 and JDK11S
On 07/03/2025 11: 04, Shruthi . wrote: Yes Alan. We have identified the
following files that
On 14/03/2025 09:22, Shruthi . wrote:
The issue which we are seeing is not reproducible in JDK21 or higher
version
Okay, so you might be chasing a different issue? For the JDK then maybe
we need more stress tests for async close, maybe that would help you
reproduce it with main line.
-Alan
On 14/03/2025 06:16, Shruthi . wrote:
Thanks Alan. I’ll port the patch you attached. It’s not a clean port
to *JDK 17*, partly because |UnixDispatcher.java| is missing. I’m
making the necessary changes manually. Once the build is ready, I’ll
validate it and update you on the results.
--
On 07/03/2025 11:04, Shruthi . wrote:
Yes Alan. We have identified the following files that require reordering.
src/java.base/share/classes/sun/nio/ch/DatagramChannelImpl.java
src/java.base/share/classes/sun/nio/ch/NioSocketImpl.java
src/java.base/share/classes/sun/nio/ch/ServerSocketChannelImpl
needed to port the fix to JDK17 and JDK11S
On 26/02/2025 10: 58, Shruthi . wrote: Hi Alan, We checked with AIX team. And
they are saying that It will be queued initially and in next few milli seconds
it will be handled. Thanks for the reply. I'll get back to you soon on how this
might
2:55 PM
To: Shruthi . ; net-dev@openjdk.org
Cc: Syed Moinudeen ; SREENIVAS MAKINEEDI
Subject: [EXTERNAL] Re: Suggestion needed to port the fix to JDK17 and JDK11S
On 07/03/2025 09: 17, Shruthi . wrote: Hi Alan, Did you get a chance to review
the fix that we have shared. It's on my li
On 07/03/2025 09:17, Shruthi . wrote:
Hi Alan,
Did you get a chance to review the fix that we have shared.
It's on my list to respond to. Note that the changes to allow for
pending signals are disruptive, impact many classes. The changes that
were proposed here only address the issue for A
On 26/02/2025 10:58, Shruthi . wrote:
Hi Alan,
We checked with AIX team. And they are saying that It will be queued
initially and in next few milli seconds it will be handled.
Thanks for the reply. I'll get back to you soon on how this might work.
Note that it will require changes in 5 cha
Moinudeen
Subject: [EXTERNAL] Re: Suggestion needed to port the fix to JDK17 and JDK11S
On 25/02/2025 08: 35, Shruthi . wrote: Hi Alan, Below is the response we got
from the AIX team. ===>what happens if pthread_kill(thread, SGRTMAX-1) is
called and the target thread is NOT in the read/wr
Cc: Syed Moinudeen
Subject: Re: [EXTERNAL] Re: Suggestion needed to port the fix to JDK17 and
JDK11S
Hi Alan,
We have reached out to the AIX team regarding your query and we are waiting
their response. Meanwhile, we are also investigating the issue. Based on the
logs, it appears that the bl
On 25/02/2025 08:35, Shruthi . wrote:
Hi Alan,
Below is the response we got from the AIX team.
===>what happens if pthread_kill(thread, SGRTMAX-1) is called and the
target thread is NOT in the read/write syscalls
The expected behavior is thread will get interrupted and it will call
the signal
From: Alan Bateman
Sent: Friday, February 14, 2025 2:14 PM
To: Shruthi . ; net-dev@openjdk.org
Cc: Syed Moinudeen
Subject: [EXTERNAL] Re: Suggestion needed to port the fix to JDK17 and JDK11S
This Message Is From an External Sender
This message came from outside
On 14/02/2025 08:18, Shruthi . wrote:
Hi Alan,
Reordering |preClose()| in AIX resolves the customer issue. We have
validated the fix, and the customer has confirmed it as well.
It may have resolved your customer issue but I'm not yet convinced it's
a robust workaround for the AIX issue. Can
19 matches
Mail list logo
