Login
Log in using an SSO provider:
Fedora Account System
Red Hat Associate
Login using a Red Hat Bugzilla account
Forgot Password
Create an Account
Red Hat Bugzilla – Bug 874196
Home
New
Search
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh94 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
[?]
This site requires JavaScript to be enabled to function correctly, please enable it.
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...
Keywords
:
Status
:
ON_QA
Alias:
None
Product:
JBoss Enterprise SOA Platform 5
Classification:
JBoss
Component:
JBossESB
Sub Component:
---
Version:
5.3.1
Hardware:
Unspecified
OS:
Unspecified
Priority:
medium
Severity:
high
Target Milestone:
---
Target Release
:
---
Assignee:
Mike Harvey
QA Contact:
Docs Contact:
URL:
http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
SOA-3554
Blocks:
TreeView+
depends on
/
blocked
Reported:
2012-11-07 16:57 UTC by
Rick Wagner
Modified:
2023-05-15 19:53 UTC (
History
)
CC List:
2 users
(
show
)
soa-p-jira
tcunning
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.
Clone Of:
SOA-3554
Environment:
SOA-P 5.x (5.1, 5.2)
Last Closed:
Type:
Bug
Embargoed:
Attachments
(Terms of Use)
Links
System
ID
Private
Priority
Status
Summary
Last Updated
Red Hat Issue Tracker
JBESB-3872
0
Major
Closed
Reformat exception in SOAPClient on http 500
2013-07-26 18:50:21 UTC
Red Hat Issue Tracker
SOA-3554
0
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> 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.