Issue Details (XML | Word | Printable)

Key: GLASSFISH-17754
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: shreedhar_ganapathy
Reporter: rlsgf
Votes: 0
Watchers: 1

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

Monitoring does not start automatically

Created: 16/Nov/11 03:08 PM   Updated: 11/Jan/12 04:28 PM
Component/s: None
Affects Version/s: 3.1_b43
Fix Version/s: None

Time Tracking:
Not Specified


Windows Server 2008R2

Participants: rlsgf and shreedhar_ganapathy

 Description  « Hide

When Glassfish starts, monitoring data is not published until some form of activity occurs.
Using JMX monitoring, values are unknown until activity, sometimes unrelated occurs.

We have tried "pinging JDBC pools" and re-enabling monitoring. Sometimes one works, some times others.

It would seem that JMX values should be published on startup.

rlsgf added a comment - 11/Jan/12 04:28 PM

My other monitor/thread issues seem better in 3.1.1-b12, however this one does not.
When starting glassfish, monitor values show as {Unknown} until activity starts.
This is minor, but odd.