-
Bug
-
Resolution: Done
-
Critical
-
7.2.0.GA
-
-
-
-
-
-
+
-
https://github.com/apache/cxf/commit/b1256efdc57465858d41586ca32cbe6c42355ed6, https://github.com/apache/cxf/commit/5021ff0fd5bbb1f5a9258745780e8863db7ad3a9, https://github.com/apache/cxf/commit/f16c5b27e4c4668ae54c66881e4a3a9bb6841994, https://github.com/apache/cxf/commit/c3fb43cd1b6f86f9bbf62f7262349f2905b985a8, https://github.com/apache/cxf/commit/fc4f94f663db6a27d2352a9b6424e42c89f7a522, https://github.com/apache/cxf/commit/5a4fd020bc87a552345425541bb62a35b0e5d8b7, https://github.com/apache/cxf/commit/53e45f515d36a31d99d0eab4e1776e5a17eeba55
There is a leak using CXF JMS transport solved with the CXF-8161.
It has been reproduced using Fuse on EAP on the ENTESB-13592 but it uses the EAP CXF implementation (cxf-rt-transports-jms-3.2.5.redhat-00001.jar).
Beware that CXF-8161 fix creates a regression fixed with the CXF-8259.
- clones
-
ENTESB-13592 CXF over JMS: Connections leak after broker recovery
- Done
- is incorporated by
-
JBEAP-19695 [GSS](7.3.z) Upgrade Apache CXF from 3.3.5 to 3.3.7
- Closed
- links to