Bug 1077262
| Summary: | [GSS] (6.2.x) HttpServletRequestSnapshot is not created for requests with WSA ReplyTo prop set | |||
|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Kyle Lape <klape> | |
| Component: | Web Services | Assignee: | Alessio Soldano <asoldano> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Rostislav Svoboda <rsvoboda> | |
| Severity: | unspecified | Docs Contact: | Russell Dickenson <rdickens> | |
| Priority: | unspecified | |||
| Version: | 6.2.0 | CC: | bmaxwell, cdewolf, ehugonne, jbliznak, myarboro, smumford | |
| Target Milestone: | CR1 | |||
| Target Release: | EAP 6.2.4 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| 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.
|
Story Points: | --- | |
| Clone Of: | 1077259 | |||
| : | 1077263 (view as bug list) | Environment: | ||
| Last Closed: | 2014-08-07 12:12:35 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | 1077259 | |||
| Bug Blocks: | 1067534, 1069354, 1077263, 1087653 | |||
|
Description
Kyle Lape
2014-03-17 15:24:13 UTC
CXF-5602 is sort-of dependent on CXF-5116, so I'm adding it here. Alessio Soldano <asoldano> updated the status of jira JBWS-3773 to Resolved 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 |