When using Apache CXF (through JBossWS integration) on top of JBoss AS 7 (whose web layer is based on JBoss Web, basically a fork of Tomcat), I'm still seeing the defect previously dealt with in https://issues.apache.org/jira/browse/CXF-2911 . This time, however, the MEP is not oneway, but a request-response one with WS-Addressing enabled and the ReplyTo header property specified to a non generic address.
The net effect is that a HTTP 202 response is immediately dispatched to the caller, letting Tomcat recycle the underlying httpservlet request.
CXF-5602 is sort-of dependent on CXF-5116, so I'm adding it here.
Flagged as Known Issue as ticket unresolved at the time of writing the release note.
Alessio Soldano <email@example.com> updated the status of jira JBWS-3773 to Resolved
Solved by update https://bugzilla.redhat.com/show_bug.cgi?id=1087653
Moving to ER4 since ER3 is the new beta candidate, and is ER2+beta blockers only
Verified on 6.3.0.ER4
I verified that reproducers from customer case test the problem.
I tried to run them with results:
all failed on 6.3.0.ER3
all passed on 6.3.0.ER4
I also checked that all fixes for CXF-5602 and CXF-5116 are really included in CXF 2.7.11
Alessio Soldano <firstname.lastname@example.org> updated the status of jira JBWS-3773 to Closed