Issue Details (XML | Word | Printable)

Key: GLASSFISH-5979
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Byron Nevins
Reporter: abien
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
glassfish

Lack Of CallFlow Monitoring

Created: 07/Sep/08 05:21 AM   Updated: 05/Apr/11 01:10 PM
Component/s: monitoring
Affects Version/s: V3
Fix Version/s: future release

Time Tracking:
Not Specified

Environment:

Operating System: other
Platform: All


Issuezilla Id: 5,979
Tags:
Participants: abien, Byron Nevins and Tom Mueller


 Description  « Hide

Server: Glassfish v3 b23

In GF v2 CallFlow was a convenient way to easily debug and monitor the
application. GF v3 is lacking such "lightweight" functionality. At least a
call-tree should be visible in the console as well as "slowest" methods.

The monitoring features of GF v2 were unique comparing it to other, opensource
application servers...



Tom Mueller added a comment - 06/Jan/11 11:55 AM

User is no longer on the project. Reassigning to default assignee for monitoring.


Tom Mueller added a comment - 05/Apr/11 01:10 PM

A fix for this issue was initially identified for possible inclusion in the 3.2 release, but after further 3.2 planning, the feature or improvement did not make the cut. This issue is being targeted for a future release. If based on a reevaluation, it is targeted for 3.2, then update the "fix version" again.