JDK-8074273 : java -version use stderr instead of stdout
  • Type: Bug
  • Component: tools
  • Sub-Component: launcher
  • Affected Version: 7u75,8u40
  • Priority: P4
  • Status: Resolved
  • Resolution: Duplicate
  • OS: windows_7
  • CPU: x86_64
  • Submitted: 2015-02-24
  • Updated: 2015-03-17
  • Resolved: 2015-03-17
Related Reports
Relates :  
Relates :  
Description
FULL PRODUCT VERSION :
java version "1.7.0_75"
Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.75-b04, mixed mode)

ADDITIONAL OS VERSION INFORMATION :
Microsoft Windows [Version 6.1.7601]

A DESCRIPTION OF THE PROBLEM :
java -version use stderr instead of stdout

STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
execute java -version and the output is redirected to stderr:

java version "1.7.0_75"
Java(TM) SE Runtime Environment (build 1.7.0_75-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.75-b04, mixed mode)


REPRODUCIBILITY :
This bug can be reproduced always.


Comments
Dup of JDK-4380614
17-03-2015

- To confirm, please run the attached test case provided by the submitter. Files attached are: ProcessStreamHandler.java CommandExecutor.java ******************************************************************************************************** Tested with JDK 7, 7u80, 8, and 8u40 and confirms that the output is always using stderr. With NIO: JDK 7: FAIL JDK 7u80: FAIL JDK 8: FAIL JDK 8u40: FAIL JDK 9 ea b53: FAIL ************************************************************************************************************ - Output of the testcase with JDK 9 ea b53: >java CommandExecutor ERROR>java version "1.9.0-ea" ERROR>Java(TM) SE Runtime Environment (build 1.9.0-ea-b53) ERROR>Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b53, mixed mode) **************************************************************************************************************************
11-03-2015

Long history here.
03-03-2015

Sent an email to the submitter requesting more information: --------------------------------------------------------------------------------------- On 2/26/2015 1:41 PM, .................... wrote: > Hi Asen, > > Can you please provide the exact steps or scenario to confirm the issue reported by you? > > Thank You, -----------------------------------------------------------------------------------------
26-02-2015