Bug 1077262 - [GSS] (6.2.x) HttpServletRequestSnapshot is not created for requests with WSA ReplyTo prop set
Summary: [GSS] (6.2.x) HttpServletRequestSnapshot is not created for requests with WSA...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Services
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.2.4
Assignee: Alessio Soldano
QA Contact: Rostislav Svoboda
Russell Dickenson
URL:
Whiteboard:
Depends On: 1077259
Blocks: eap62-cp04-blockers 1069354 1077263 1087653
TreeView+ depends on / blocked
 
Reported: 2014-03-17 15:24 UTC by Kyle Lape
Modified: 2018-12-05 17:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In previous versions of JBoss EAP 6, the servlet request object would, under certain circumstances, not be cloned before queuing a request with the WSA replyTo property set to be processed on a different thread. As a consequence, JBossWeb would recycle the stale request object after the initiator received its acknowledgment response, causing invalid data to be used when the endpoint implementation tries to access the stale request object. This release ensures the servlet request object is cloned when it needs to be and invalid data is no longer used by endpoint implementations that execute on a different thread than the original HTTP request.
Clone Of: 1077259
: 1077263 (view as bug list)
Environment:
Last Closed: 2014-08-07 12:12:35 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Apache JIRA CXF-5116 0 None None None Never
Apache JIRA CXF-5602 0 None None None Never
Red Hat Issue Tracker JBWS-3773 0 Major Closed HttpServletRequest in WebServiceContext and requests with WSA ReplyTo prop set 2017-03-29 14:47:56 UTC

Description Kyle Lape 2014-03-17 15:24:13 UTC 
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.
Comment 1 Kyle Lape 2014-03-24 22:10:19 UTC 
CXF-5602 is sort-of dependent on CXF-5116, so I'm adding it here.
Comment 3 JBoss JIRA Server 2014-04-23 10:20:22 UTC 
Alessio Soldano <asoldano> updated the status of jira JBWS-3773 to Resolved
Comment 5 Jan Blizňák 2014-06-19 09:29:41 UTC 
Verified with 6.2.4.CP.CR1

I used reproducer from customer case, verified that reproducer from customer case tests the problem and run it with results:

failed on 6.2.3
passed on 6.2.4.CP.CR1
Comment 6 JBoss JIRA Server 2015-04-25 20:30:15 UTC 
Alessio Soldano <asoldano> updated the status of jira JBWS-3773 to Closed
Note You need to log in before you can comment on or make changes to this bug.