You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Donald Woods (JIRA)" <ji...@apache.org> on 2007/02/23 15:31:05 UTC
[jira] Created: (GERONIMO-2878) JVM stats exposed through JMX are
incorrect and missing init/max heap size
JVM stats exposed through JMX are incorrect and missing init/max heap size
--------------------------------------------------------------------------
Key: GERONIMO-2878
URL: https://issues.apache.org/jira/browse/GERONIMO-2878
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: management
Affects Versions: 2.0
Environment: WinXP, Java 1.5.0_11, JMX Viewer
Reporter: Donald Woods
Assigned To: Donald Woods
Fix For: 2.0
The statistics for geronimo:J2EEServer=geronimo,name=JVM,j2eeType=JVM are:
1) incorrect for JVM Up Time, which shows 1171999222859 msecs. after only about 10 mins.
2) does not provide init or max Heap size values for health monitoring - http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/MemoryUsage.html
3) does not provide all of the JVM attributes, as the JVM portlet does
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2878) JVM stats exposed through JMX are
incorrect and missing init/max heap size
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated GERONIMO-2878:
-----------------------------------
Fix Version/s: (was: 2.0.x)
2.0
I'm going to try and get this into 2.0.
> JVM stats exposed through JMX are incorrect and missing init/max heap size
> --------------------------------------------------------------------------
>
> Key: GERONIMO-2878
> URL: https://issues.apache.org/jira/browse/GERONIMO-2878
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: management
> Affects Versions: 2.0-M5
> Environment: WinXP, Java 1.5.0_11, JMX Viewer
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0
>
>
> The statistics for geronimo:J2EEServer=geronimo,name=JVM,j2eeType=JVM are:
> 1) incorrect for JVM Up Time, which shows 1171999222859 msecs. after only about 10 mins.
> 2) does not provide init or max Heap size values for health monitoring - http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/MemoryUsage.html
> 3) does not provide all of the JVM attributes, as the JVM portlet does
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-2878) JVM stats exposed through JMX are
incorrect and missing init/max heap size
Posted by "Prasad Kashyap (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prasad Kashyap updated GERONIMO-2878:
-------------------------------------
Fix Version/s: (was: 2.0-M7)
2.0.x
> JVM stats exposed through JMX are incorrect and missing init/max heap size
> --------------------------------------------------------------------------
>
> Key: GERONIMO-2878
> URL: https://issues.apache.org/jira/browse/GERONIMO-2878
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: management
> Affects Versions: 2.0-M5
> Environment: WinXP, Java 1.5.0_11, JMX Viewer
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0.x
>
>
> The statistics for geronimo:J2EEServer=geronimo,name=JVM,j2eeType=JVM are:
> 1) incorrect for JVM Up Time, which shows 1171999222859 msecs. after only about 10 mins.
> 2) does not provide init or max Heap size values for health monitoring - http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/MemoryUsage.html
> 3) does not provide all of the JVM attributes, as the JVM portlet does
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2878) JVM stats exposed through JMX are
incorrect and missing init/max heap size
Posted by "Marcos Hack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477867 ]
Marcos Hack commented on GERONIMO-2878:
---------------------------------------
Hi Donald,
About JVM Up Time, "1171999222859 ms" is a time stamp, the number of milliseconds since Jan/1/1970, not since JVM was started.
And about memory information and all another JVM attributes, maybe you can use JVM JMX agent [1] in place of geronimos ones.
Regards,
Marcos Hack.
[1] http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html
> JVM stats exposed through JMX are incorrect and missing init/max heap size
> --------------------------------------------------------------------------
>
> Key: GERONIMO-2878
> URL: https://issues.apache.org/jira/browse/GERONIMO-2878
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: management
> Affects Versions: 2.0
> Environment: WinXP, Java 1.5.0_11, JMX Viewer
> Reporter: Donald Woods
> Assigned To: Donald Woods
> Fix For: 2.0
>
>
> The statistics for geronimo:J2EEServer=geronimo,name=JVM,j2eeType=JVM are:
> 1) incorrect for JVM Up Time, which shows 1171999222859 msecs. after only about 10 mins.
> 2) does not provide init or max Heap size values for health monitoring - http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/MemoryUsage.html
> 3) does not provide all of the JVM attributes, as the JVM portlet does
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-2878) JVM stats exposed through JMX are
incorrect and missing init/max heap size
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12516410 ]
Donald Woods commented on GERONIMO-2878:
----------------------------------------
>From http://java.sun.com/j2se/1.5.0/docs/guide/management/jconsole.html - Uptime: Total amount of time since the JVM was started.
A "Time" attribute would be the current OS time since 1970...
Since we now require Java 5 or later, I'm going to use the new in VM ManagementFactory to get the actual JVM provided mxbean for the correct results.
> JVM stats exposed through JMX are incorrect and missing init/max heap size
> --------------------------------------------------------------------------
>
> Key: GERONIMO-2878
> URL: https://issues.apache.org/jira/browse/GERONIMO-2878
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: management
> Affects Versions: 2.0-M5
> Environment: WinXP, Java 1.5.0_11, JMX Viewer
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0
>
>
> The statistics for geronimo:J2EEServer=geronimo,name=JVM,j2eeType=JVM are:
> 1) incorrect for JVM Up Time, which shows 1171999222859 msecs. after only about 10 mins.
> 2) does not provide init or max Heap size values for health monitoring - http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/MemoryUsage.html
> 3) does not provide all of the JVM attributes, as the JVM portlet does
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-2878) JVM stats exposed through JMX are
incorrect and missing init/max heap size
Posted by "Donald Woods (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-2878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods closed GERONIMO-2878.
----------------------------------
Resolution: Fixed
Fix Version/s: 2.1
Only updated the existing Uptime and Heap value calculations, as adding new Stats would break our compatibility with the JEE Management Spec 1.0.
Committed revision 561093 in branches/2.0
Committed revision 561094 in trunk (2.1)
Verified UpTime values are fixed and the reworked Heap values work correctly via JMX portlet -
Name Value
JVM Heap Size: Description: The memory usage of the JVM
Unit: BYTE
Start Time: Mon Jul 30 14:53:31 EDT 2007
Last Sample Time: Mon Jul 30 14:54:40 EDT 2007
Upper Bound: 532742144
Lower Bound: 0
High Water Mark: 27070456
Low Water Mark: 24755024
Current: 24755024
JVM Up Time: Description: The length of time that the JVM has been running
Unit: MILLISECOND
Start Time: Mon Jul 30 14:53:31 EDT 2007
Last Sample Time: Mon Jul 30 14:54:40 EDT 2007
Count: 69500
> JVM stats exposed through JMX are incorrect and missing init/max heap size
> --------------------------------------------------------------------------
>
> Key: GERONIMO-2878
> URL: https://issues.apache.org/jira/browse/GERONIMO-2878
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: management
> Affects Versions: 2.0-M5
> Environment: WinXP, Java 1.5.0_11, JMX Viewer
> Reporter: Donald Woods
> Assignee: Donald Woods
> Fix For: 2.0, 2.1
>
>
> The statistics for geronimo:J2EEServer=geronimo,name=JVM,j2eeType=JVM are:
> 1) incorrect for JVM Up Time, which shows 1171999222859 msecs. after only about 10 mins.
> 2) does not provide init or max Heap size values for health monitoring - http://java.sun.com/j2se/1.5.0/docs/api/java/lang/management/MemoryUsage.html
> 3) does not provide all of the JVM attributes, as the JVM portlet does
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.