-
Bug
-
Resolution: Done
-
Major
-
2.0.14.Final, 2.0.15.Final, 2.0.16.Final, 2.0.17.Final
-
None
We're seeing undertow slowly continuing a memory consumption until we run out of heap space and start getting outofmemory errors. On analysis of the heapdump, the main suspect appears to be:
One instance of "io.undertow.server.protocol.http.HttpOpenListener" loaded by "sun.misc.Launcher$AppClassLoader @ 0xc0041e40" occupies 967,912,832 (95.19%) bytes. The memory is accumulated in one instance of "java.util.concurrent.ConcurrentHashMap$Node[]" loaded by "<system class loader>".
This happened immediately when moving from 1.4.22.Final to 2.0.16.Final. I suspect its being triggered by a poorly designed health check.
- is cloned by
-
JBEAP-16434 (7.2.z) [UNDERTOW-1486] Out of memory errors
- Closed
- relates to
-
WFLY-11691 Default no-request-timeout value on HTTP(s) listeners seems to be causing unexpected timeouts
- Closed
-
WFLY-17307 Default no-request-timeout value on HTTP(s) listeners seems to be causing unexpected timeouts
- Open