|Re: [jetty-users] Updating SSL keystore|
Hi, On Thu, Feb 9, 2017 at 12:56 PM, Travis Spencer <travislspencer@xxxxxxxxx> wrote: > Jetty and our server are in the same address space and we provide a tailored > configuration and management service in that same box. Requiring admins to > use our API for all things except changing thread count where they must use > an alternative API, JMX, isn't an option because of UX, security, etc. > reasons. So, Jetty requiring us to use this API isn't desirable and I really > don't see why that is a requirement from the Jetty side. Can the mbean be > used directly from within our app that is embedding Jetty while the JMX > server remains disabled? If not, some low level API is needed from Jetty > IMO because pushing the requiment for JMX on apps isn't always reasonable, > as in our case. The API is already there. You just need to call it from your management system, I guess in the same way you have wired up the call to reload the SslContextFactory. -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts.
Back to the top