Bug 874196
| Summary: | RollupClone - New Behavior for consideration-- on HTTP 500, have SOAPClient throw an Exception that is palatable downstream | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise SOA Platform 5 | Reporter: | Rick Wagner <rwagner> |
| Component: | JBossESB | Assignee: | Mike Harvey <mharvey> |
| Status: | ON_QA --- | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 5.3.1 | CC: | soa-p-jira, tcunning |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/SOA-3554 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
When SOAPClient is used and an HTTP 500 Error is encountered, SOA-P throws an Exception containing the HTTP 500 stack trace which is not handled by ActionProcessingPipeline, resulting in an uninformative message.
|
Story Points: | --- |
| Clone Of: | SOA-3554 | Environment: |
SOA-P 5.x (5.1, 5.2)
|
| Last Closed: | 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: | 781067 | ||
| Bug Blocks: | |||
|
Comment 1
JBoss JIRA Server
2012-11-20 19:32:22 UTC
|