Simone Bordet
Simone Bordet
The dump above shows a perfectly normal, idle, `HttpClient` with 1 destination that has 4 connections, that have been used each for ~2.5M requests (so a total of ~10M requests)....
I'm not sure I understand this, as all seems unrelated to Jetty? Why it is a Jetty bug if the HSM times out?
Jetty does not call `KeyStore.getKey()`. Jetty just uses the `KeyStore` from the JDK implementation to _set_ values to configure it, and then the JDK implementation does the rest, which may...
> But it might be considered to log this particular error with level error and not debug because it's something that leads to the inoperation of Jetty, so the reason...
> A client closing a connection is leading to a ProviderException? A client can cause a large number of different exceptions, and we rarely differentiate -- it's a bad client...
@joakime those are not good as they only convey information for bean _property_ changes. For JMX we would need JMX metadata and cover the `invoke()` semantic.
I'll look into this.
No, `AttributeChangeNotification` must be emitted by the MBean implementation itself. We don't do that in `ObjectMBean` ourselves. There is no standard for operation notifications. It would be impossible to detect...
There are 2 approaches: 1. Introduce `ObjectMBean.Listener` as a custom interface so that application can register listeners and be notified of attribute events or invocation 1. Use JMX built-in `NotificationEmitter`...
See also comments in #3517.