Bug 874196 - RollupClone - New Behavior for consideration-- on HTTP 500, have SOAPClient throw an Exception that is palatable downstream
Summary: RollupClone - New Behavior for consideration-- on HTTP 500, have SOAPClient t...
Status: ON_QA
Alias: None
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: JBossESB   
(Show other bugs)
Version: 5.3.1
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: ---
Assignee: Mike Harvey
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Keywords:
Depends On: SOA-3554
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-07 16:57 UTC by Rick Wagner
Modified: 2018-12-02 19:19 UTC (History)
3 users (show)

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: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


External Trackers
Tracker ID Priority Status Summary Last Updated
JBoss Issue Tracker JBESB-3872 Major Closed Reformat exception in SOAPClient on http 500 2013-07-26 18:50:21 UTC
JBoss Issue Tracker SOA-3554 Major Closed New Behavior for consideration-- on HTTP 500, have SOAPClient throw an Exception that is palatable downstream 2013-07-26 18:50:21 UTC

Comment 1 JBoss JIRA Server 2012-11-20 19:32:22 UTC 
Tom Cunningham <tcunning@redhat.com> updated the status of jira JBESB-3872 to Closed
Note You need to log in before you can comment on or make changes to this bug.