Fatal errors and warnings produced by the VM are sent to stdout and
not stderr.
###@###.### 2001-08-31
Name: gm110360 Date: 02/21/2002
FULL PRODUCT VERSION :
Sorry, I'm not at the machine where this condition occurs, but it's j2sdk 1.4.0
rc1 for Linux.
FULL OPERATING SYSTEM VERSION :
FreeBSD 4.0 -- Lunux compatibility (I know this is not a
supported platform)
A DESCRIPTION OF THE PROBLEM :
The "bug" I'm reporting is that HotSpot writes error
messages to standard output. It would be more appropriate
to write them to standard error, the conventional place for
error messages. Going to standard output, they not only
mess up program output breaking data pipelines, but the
messages can easily be missed since they are likely to be
piped or otherwise redirected. Running this way makes the
Java runtime product appear "unfinished".
I am not complaining about the actual error that is
occurring, especially since this is probably an unsupported
configuration. But, IN CASE YOU'RE INTERESTED, the Linux
version appears to run okay under FreeBSD (4.0) Linux,
compatibility mode, but as it cleans up upon program
termination, it outputs one or more messages about not
being able to uninstall signal handlers (probably one
message per thread). Otherwise the termination proceeds
okay -- so the messages appearing on standard output are
particularly annoying!
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Run any Java program under FreeBSD (4.0) Linux
compatibility mode.
2.
3.
EXPECTED VERSUS ACTUAL BEHAVIOR :
HotSpot error messages are written to standard output.
Would be better if written to standard error. Would be even
better if errors didn't occur at all!
ERROR MESSAGES/STACK TRACES THAT OCCUR :
Sorry, since I'm not writing this from the environment where the problem
occurred, I cannot provide the exact message text. They are messages from
HotSpot announcing that signal handlers cannot be uninstalled.
This bug can be reproduced always.
(Review ID: 138896)
======================================================================
not stderr.
###@###.### 2001-08-31
Name: gm110360 Date: 02/21/2002
FULL PRODUCT VERSION :
Sorry, I'm not at the machine where this condition occurs, but it's j2sdk 1.4.0
rc1 for Linux.
FULL OPERATING SYSTEM VERSION :
FreeBSD 4.0 -- Lunux compatibility (I know this is not a
supported platform)
A DESCRIPTION OF THE PROBLEM :
The "bug" I'm reporting is that HotSpot writes error
messages to standard output. It would be more appropriate
to write them to standard error, the conventional place for
error messages. Going to standard output, they not only
mess up program output breaking data pipelines, but the
messages can easily be missed since they are likely to be
piped or otherwise redirected. Running this way makes the
Java runtime product appear "unfinished".
I am not complaining about the actual error that is
occurring, especially since this is probably an unsupported
configuration. But, IN CASE YOU'RE INTERESTED, the Linux
version appears to run okay under FreeBSD (4.0) Linux,
compatibility mode, but as it cleans up upon program
termination, it outputs one or more messages about not
being able to uninstall signal handlers (probably one
message per thread). Otherwise the termination proceeds
okay -- so the messages appearing on standard output are
particularly annoying!
STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
1. Run any Java program under FreeBSD (4.0) Linux
compatibility mode.
2.
3.
EXPECTED VERSUS ACTUAL BEHAVIOR :
HotSpot error messages are written to standard output.
Would be better if written to standard error. Would be even
better if errors didn't occur at all!
ERROR MESSAGES/STACK TRACES THAT OCCUR :
Sorry, since I'm not writing this from the environment where the problem
occurred, I cannot provide the exact message text. They are messages from
HotSpot announcing that signal handlers cannot be uninstalled.
This bug can be reproduced always.
(Review ID: 138896)
======================================================================
- duplicates
-
JDK-4637577 Improve JNI_CreateJavaVM error message output
-
- Closed
-
-
JDK-6221838 No VM messages (by default) should ever be sent down stdout, stdout belongs to the app
-
- Closed
-
- relates to
-
JDK-4837953 VM stdout/stderr/logging cleanup
-
- Closed
-