Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
2.1.2
-
None
Description
I observed memory leak (OOM thrown) in following situations:
1.WS-Addressing enabled on client and server side. When server stops responding (connection refused on client side)
client memory usage is increasing until OOM is thrown.
2.WS-Addressing enabled only on client side, server provide service without WS-Addressing feature (or WS-Addressing configuration is incorrect). Client memory heap is building up even faster than in first case.
I will provide a sample application and more detailed description how to reproduce bug.
Attachments
Attachments
Issue Links
- is related to
-
CXF-7943 MAPCodec: Memory leak due to growing uncorrelatedExchanges
- Open