Details
-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
Description
Add a stuck-thread-detector in our default configs.
A threshold of 60 seconds would probably be sufficiently large enough to avoid any large volume of unwanted warnings, but low enough to provide input on slowness that are quite large in most cases:
<server name="default-server">
<http-listener name="default" socket-binding="http" redirect-socket="https" enable-http2="true"/>
<https-listener name="https" socket-binding="https" security-realm="ApplicationRealm" enable-http2="true"/>
<host name="default-host" alias="localhost">
<location name="/" handler="welcome-content"/>
<http-invoker security-realm="ApplicationRealm"/>
<filter-ref name="stuck" />
</host>
</server>
...
<filters>
<expression-filter name="stuck" expression="blocking; stuck-thread-detector(60)"/>
</filters>
Attachments
Issue Links
- relates to
-
-
- Open
-