New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Using JMX for instance & subsystem management #1808

Open

pki-bot opened this issue Oct 3, 2020 · 2 comments

Milestone

pki-bot commented Oct 3, 2020

This issue was migrated from Pagure Issue #1246. Originally filed by edewata (@edewata) on 2015-01-23 19:15:11:

Assigned to nobody

JMX provides interface to manage and monitor Tomcat remotely (i.e. access Tomcat internals). We should investigate if JMX can be used to:

shutdown or restart the instance
deploy and undeploy a subsystem
check subsystem deployment status

If that's the case, we should investigate the implementation:

do we need to write custom MBeans?
do we need to write a management client library?
do we need to write a management CLI/UI?
how do we configure the authentication/authorization?

See also:

Proposed milestone: 10.3

pki-bot added this to the UNTRIAGED milestone

Author

pki-bot commented Oct 3, 2020

Comment from mharmsen (@mharmsen) at 2015-01-26 21:15:30

Per CS/DS meeting of 01/26/2015: 10.3

Author

pki-bot commented Oct 3, 2020

Comment from edewata (@edewata) at 2017-02-27 14:06:59

Metadata Update from @edewata:

Issue set to the milestone: UNTRIAGED

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment