Feature #6871
add JMX instrumentation to monitor the appserver agents
Start date:
Due date:
% Done:
100%
billable:
No
vendor_id:
GCD
case_num:
version_reported:
version_resolved:
reviewer:
production:
No
env_name:
topics:
Related issues
History
#2 Updated by Constantin Asofiei almost 4 years ago
Beside the Administration Console, we need JMX instrumentation, for each started appserver, with:
- agents in use (currently processing requests)
- agents available (waiting for requests)
- max number of agents
#3 Updated by Constantin Asofiei almost 4 years ago
- Related to Feature #6814: JMX instrumentation for FWD core, persistance and ORM layers added
#4 Updated by Constantin Asofiei almost 4 years ago
The tracing should include the agent's PID, too, as currently this is being used in some logging files.
#5 Updated by Constantin Asofiei over 3 years ago
JMX instrumentation for appserver agent state was added to 3821c/14333.
#6 Updated by Constantin Asofiei over 3 years ago
Added documentation for available JMX instrumentation at Available JMX Instrumentation
#7 Updated by Greg Shah over 3 years ago
It is really good. I made some minor tweaks.
#8 Updated by Greg Shah over 1 year ago
- Related to Feature #1847: improve server instrumentation added
#9 Updated by Greg Shah over 1 year ago
- Related to Feature #6377: provide tooling (and UI in the admin interface) to manage appserver agents (start/stop/bounce) added
#10 Updated by Greg Shah over 1 year ago
We can close this, right?
#11 Updated by Constantin Asofiei over 1 year ago
Yes
#12 Updated by Greg Shah over 1 year ago
- % Done changed from 0 to 100
- Status changed from New to Closed
- Assignee set to Constantin Asofiei