|[jetty-users] Trying to control DosFilter parameters using JMX via MANAGED_ATTRIBUTES.|
I have a webapp on which I have included a DoSFilter on all endpoints. I want to be able to configure the DosFilter parameters using JMX. So far I’ve been able to connect to Jetty JVM using jconsole and see all the available Mbeans. I have added the following in my deployment descriptor
Where DoSFilter is the name of my Filter (org.eclipse.jetty.servlets.DoSFiler).
I can see this filter as an MBean on Jconsole but there are no available attributes or operations with which I can control parameters like maxRequestPerSec or ipWhitelist.
Am I doing anything wrong here?
From: jetty-users-bounces@xxxxxxxxxxx [mailto:jetty-users-bounces@xxxxxxxxxxx]
On Behalf Of Bill Harten
Browsers fail to connect to Jetty 8 when using a wildcard SSL certificate. Can Jetty be used with wildcard certificates? Any special setup?
Firefox says 'Peer reports it experienced an internal error. (Error code: ssl_error_internal_error_alert)'. Other browsers just say 'SSL Connection Error'. Many internet posts about this but no solutions.
Using java SE 1.6 and 1.7. Jetty is embedded via java methods not XML. Ordinary non-wildcard certs are working.
Back to the top