Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

IBM Java Version shows incorrect version number

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Trivial Trivial
  • Resolution: Deferred
  • Affects Version/s: 4.3
  • Fix Version/s: None
  • Component/s: UI / UX
  • Environment:
    HQ-server 4.3.0-EE-1382 running on CentOS 5.2
    HQ-agent 4.3.0-EE-1382 running on CentOS 5.3
  • Case Links:
    none
  • Regression:
    No

Description

IBM Java Version shows incorrect version number when looking at the metrics for an HQ Monitor Agent running IBM JVM

Expected Result:
The version displayed in the UI should match that of running 'java -version' or 'java -fullversion' from the command line

Actual Result:
The version number displayed in the UI does NOT match that from the command line

Steps to reproduce:
1. Log into the HQ Server Dashboard
2. Browse for an HQ Agent running IBM JVM
3. Ensure Java Vendor indicates IBM Corporation
4. Note the Java Version
5. Log into the Server housing the same HQ Agent running IBM JVM
6. At the command line, enter 'java -version' and 'java -fullversion'
7. Note the Java Version:
8. Compare the Java Version between the UI and the command line
9. Note the two Java Versions do not match

Work around:
N\A - does not affect functionality

Additional Notes:
This issue was also reproduced on 4.2.0-EE

Please see screenshot for UI displaying Java Version.

For the same HQ Agent, the command line result is:

  1. java -version
    java version "1.6.0"
    Java(TM) SE Runtime Environment (build pxa6460sr2-20080818_01(SR2))
    IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux amd64-64 jvmxa6460-20080816_22093 (JIT enabled, AOT enabled)
    J9VM - 20080816_022093_LHdSMr
    JIT - r9_20080721_1330ifx2
    GC - 20080724_AA)
    JCL - 20080808_02
  1. java -fullversion
    java full version "JRE 1.6.0 IBM Linux build pxa6460sr2-20080818_01 (SR2) "

Activity

Hide
Todd Rader added a comment -

Can you compile and run the following program on the platform – be sure that javac and java are from the proper IBM JVM:

~/work/version> cat Version.java

public class Version {
public static void main(String[] args) { System.out.println("Version is " + System.getProperty("java.version")); }
}
~/work/version> javac Version.java
~/work/version> java Version
Version is 1.5.0_22

Show
Todd Rader added a comment - Can you compile and run the following program on the platform – be sure that javac and java are from the proper IBM JVM: ~/work/version> cat Version.java public class Version { public static void main(String[] args) { System.out.println("Version is " + System.getProperty("java.version")); } } ~/work/version> javac Version.java ~/work/version> java Version Version is 1.5.0_22
Hide
Frederic Calindas added a comment -

Running the above program on the platform with javac and java from the proper IBM JVM results as:

  1. ls -l /usr/bin | grep java
    lrwxrwxrwx 1 root root 41 Mar 24 14:52 java -> /sw/IBM/WebSphere/AppServer/java/bin/java
    lrwxrwxrwx 1 root root 42 Mar 25 11:45 javac -> /sw/IBM/WebSphere/AppServer/java/bin/javac
  1. cat Version.java
    public class Version {
    public static void main(String[] args) { System.out.println("Version is " + System.getProperty("java.version")); }
    }
  2. javac Version.java
  3. java Version
    Version is 1.6.0
Show
Frederic Calindas added a comment - Running the above program on the platform with javac and java from the proper IBM JVM results as:
  1. ls -l /usr/bin | grep java lrwxrwxrwx 1 root root 41 Mar 24 14:52 java -> /sw/IBM/WebSphere/AppServer/java/bin/java lrwxrwxrwx 1 root root 42 Mar 25 11:45 javac -> /sw/IBM/WebSphere/AppServer/java/bin/javac
  1. cat Version.java public class Version { public static void main(String[] args) { System.out.println("Version is " + System.getProperty("java.version")); } }
  2. javac Version.java
  3. java Version Version is 1.6.0
Hide
Frederic Calindas added a comment -

Additional information... looking at the WebSphere Node Server, the correct Java Version is specified for the IBM JVM.

Show
Frederic Calindas added a comment - Additional information... looking at the WebSphere Node Server, the correct Java Version is specified for the IBM JVM.
Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    42 weeks ago