-
Notifications
You must be signed in to change notification settings - Fork 738
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Writing to closed socket connection kills the JVM #2871
Comments
None of the error handling tests are reporting failure. AttachAPI sanity test passes. |
The TestNG harness is not printing the list of passing and failing tests. the exit status of 141 is suspicious: a normal test failure causes an exit status of 1. |
Test is failing in
Console log:
attach API log:
at which point the attacher dies.
I instrumented the test to catch Throwable: no exception or other throwable is thrown. |
The test connects to a target Java process, opening a socket in the process. It then causes the target to stop (closing the socket) and tries to write to the socket. I wrote an ad-hoc test (attached):
This previously worked (i.e. threw an exception) on OpenJ9:
... and OpenJDK:
But not with the latest OpenJ9:
The first call to |
This looks like a class library change. @andrew-m-leonard Has the socket code changed recently? |
Nothing has changed in jdk10u for 2 months... extensions haven't changed from about a month either |
Fails with Java 8:
|
Java8 extensions were updated to jdk8u192-b03 recently |
Passing with the latest nightly build from openjdk version "10.0.2-adoptopenjdk" 2018-07-17 |
Failed with latest eclipse build:
** |
Bracketed it to the GCC-7.3 changes:
Those changes should affect only PPCLE:
|
The gcc 7.3 switch only occurred for Java 11 builds, yet the test is failing on older versions. |
The log is lying. There were more changes between:
Searching through those changes. |
@pdbain-ibm Please exclude TestAttachErrorHandling_SE80_0 (Java 8 ) and TestAttachErrorHandling_0 (later versions) from the OpenJ9 extended testing so all the extended tests stop failing nightly. |
@pshipton Will do. I am getting close to the root cause. |
Disable these tests while investigating issue eclipse-openj9#2871 "Writing to closed socket connection kills the JVM". [ci-skip] Signed-off-by: Peter Bain <peter_bain@ca.ibm.com>
Reverting these
To test, unpack attached archive, add the Java under test, and runt the
|
Not sure Peter's ping worked, since its quoted. |
Fix - #2965 |
omrsig.cpp::omrsig_primary_sigaction/omrsig_primary_signal doesn't support registration with SIG_DFL/SIG_IGN/NULL as the signal handler. 1) SIG_IGN is passed as the signal handler for SIGPIPE. 2) NULL is passed as the new signal handler for SIGILL. In the above cases, omrsig_primary_sigaction/omrsig_primary_signal shouldn't be used for registering a signal handler. Now onwards, only <signal.h>::sigaction/signal will used in the above cases. SIGPIPE needs to be ignored for the Java Attach API to work properly. Fixes eclipse-openj9#2871 Signed-off-by: Babneet Singh <sbabneet@ca.ibm.com>
@pshipton Interesting some of our TLS 1.3 SSL test failures fail with "Java exited with status 141", I will see if this PR has fixed that... |
Recent regression. Looks like a blocker. FYI @gacholio . I am investigating.
The text was updated successfully, but these errors were encountered: