JDK-4882974 : JVM generates duplicate warning lines
  • Type: Bug
  • Component: tools
  • Sub-Component: launcher
  • Affected Version: 1.4.2
  • Priority: P5
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2003-06-24
  • Updated: 2009-12-01
  • Resolved: 2009-12-01
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 7
7Resolved
Related Reports
Duplicate :  
Relates :  
Description

Name: dkR10031			Date: 06/24/2003



Current linux and solaris implementations of the JVM 
generates duplicate warning lines in a case when it is 
called with the '-classic' flag. There is only one 
warning line for the windows JVM implementation.
To reproduce this bug please execute java with 
the '-classic -version -Xrunjcov' options:
---------------- Test output for the linux -----------------------
bash-2.03$ uname -a
SunOS novo148 5.8 Generic_108528-20 sun4u sparc SUNW,Ultra-80
bash-2.03$ /net/linux-15/export/home/java/jdk1.4.2/sparc/bin/java -classic -version -Xrunjcov:V
Warning: classic VM not supported; client VM will be used
Warning: classic VM not supported; client VM will be used
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2-b27)
Java HotSpot(TM) Client VM (build 1.4.2-b27, mixed mode)
---------------- End of the linux test output --------------------------

======================================================================

Comments
EVALUATION With the fix for 6367077, there will be no execs if the data-model is unchanged, the rexec will occur only for unmatched data-models, where duplicate messages will be emitted. Closing this bug as a duplicate of 6367077.
01-12-2009

EVALUATION The comments are correct; this is a launcher related issue. The double warning message behavior has existed since 1.4.0 with the introduction of the C-based launcher. The main job of the launcher is to dlopen the right libjvm.so library, which is influenced by several of the command line flags such as "-client", "-server," and "-classic". The current structor of the launcher on unix systems has the launcher process re-exec itself to properly set the LD_LIBRARY_PATH variable to influence the dynamic linker. The Warning: classic VM not supported; client VM will be used message is printed once for each instance of the launcher process, the original and the exec child. I don't think this is a very serious issue so I've downgraded the severity. The cleanest way to fix this problem would be to change the launcher to not always exec by removing any dependence on LD_LIBRARY_PATH to find jre/jdk shared libraries; see bug 4769088. ###@###.### 2003-06-27
27-06-2003