https://issues.apache.org/bugzilla/show_bug.cgi?id=49821
Summary: Tomcat CLI
Product: Tomcat 7
Version: trunk
Platform: All
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P2
Component: Manager
AssignedTo: dev@tomcat.apache.org
ReportedBy: pids...@apache.org
Using JMX the CLI enables simple status checks of hosts, apps and connectors;
it also permits an application to be reloaded, deployed and undeployed. The
'find leaks' function is also exposed.
The targeted process is identified either by passing a PID, JMX URI, or a JMX
port. The CLI can also exploit Java 6 management features to connect to a
process localised JMX/RMI connector.
A number of additional strategies are possible, including using the
non-standard* Attach API in the Sun/Oracle JVM to enable a management agent and
initialise a local JMX/RMI connector if one is not active.
This, in effect, means that for a single Tomcat running it would be possible to
guess which process is the correct target process, attach to it, inject an
agent and then connect via JMX, all without having to perform manual JMX
configuration.
I will attach code shortly.
* So reflection is used, allowing the CLI to degrade gracefully on other JVMs.
In theory, at least.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
