-
Enhancement
-
Resolution: Fixed
-
P4
-
17, 21, 25
-
b23
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8367111 | 21.0.10 | Paul Hohensee | P4 | Resolved | Fixed | master |
When jspawnhelper fails for whatever reason, but more prominently due to JDK-8325621, it will report the errors into stdout, but not to the relevant IOException. So, if the application is configured to only capture the exception logs (e.g. through java.util.logging), we will miss any output from jspawnhelper, it user would be left without a clue what have happened. We have seen customers spending weeks trying to figure out what went wrong.
It would be good to provide useful IOException when jspawnhelper fails. We already have a precedent with vmError printing helpful suggestions when VM fails, we can do the same here. Something like: https://github.com/openjdk/jdk/compare/master...shipilev:JDK-8352533-jspawnhelper-ioexceptions
It would be good to provide useful IOException when jspawnhelper fails. We already have a precedent with vmError printing helpful suggestions when VM fails, we can do the same here. Something like: https://github.com/openjdk/jdk/compare/master...shipilev:JDK-8352533-jspawnhelper-ioexceptions
- backported by
-
JDK-8367111 Report useful IOExceptions when jspawnhelper fails
-
- Resolved
-
- causes
-
JDK-8357436 Change jspawnhelper warning recommendation from VFORK to FORK
-
- Resolved
-
- relates to
-
JDK-8357517 (process) More helpful IOException messages in case of Runtime.exec errors
-
- New
-
- links to
-
Commit(master) openjdk/jdk21u-dev/361f1797
-
Commit(master) openjdk/jdk/5c73dfc2
-
Review(master) openjdk/jdk21u-dev/2142
-
Review(master) openjdk/jdk/24149
(2 links to)