Bug 1004314 - Response event does not have replyTo field when representing an exception
Summary: Response event does not have replyTo field when representing an exception
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: RT Governance
Version: 6.0.0 GA
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER3
: ---
Assignee: Gary Brown
QA Contact: Jiri Pechanec
URL:
Whiteboard:
Depends On:
Blocks: 1004182
TreeView+ depends on / blocked
 
Reported: 2013-09-04 11:49 UTC by Gary Brown
Modified: 2014-07-02 09:19 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RTGOV-262 0 Major Closed ReplyTo field not set in response events when exception is thrown by swyd service 2014-07-02 09:19:14 UTC

Description Gary Brown 2013-09-04 11:49:45 UTC
Description of problem:

When an exception is thrown from a service (or handler), the resulting response event does not contain a 'replyTo' id which is required to tie it to the originating request.

Version-Release number of selected component (if applicable):


How reproducible:

Use the switchyard validate-xml example, and observe the stored activity events (with tracing set to FINEST).


The normal 'replyToId' field is missing from the response.


Steps to Reproduce:
1. Deploy the validate-xml switchyard example
2. Send the invalidate example xml message
3. View the FINEST logs to see the JPAActivityStore.store method's debug info showing the json representation of the events being stored

Actual results:

[{
	"id":"f6a571b7-896a-4514-a1fa-90742f65ee88",
	"activityTypes":[{
		"type":"RequestReceived",
		"interface":"{urn:switchyard-quickstart:validate-xml:0.1.0}OrderService",
		"operation":"submitOrder",
		"serviceType":"{urn:switchyard-quickstart:validate-xml:0.1.0}OrderService",
		"messageType":"{urn:switchyard-quickstart:validate-xml:0.1.0}order",
		"context":[{"value":"ID-gbrown-redhat-54552-1378282347581-0-4","type":"Message"}],
		"unitId":"f6a571b7-896a-4514-a1fa-90742f65ee88",
		"timestamp":1378282559345
	},{
		"type":"ResponseSent",
		"interface":"{urn:switchyard-quickstart:validate-xml:0.1.0}OrderService",
		"operation":"submitOrder",
		"serviceType":"{urn:switchyard-quickstart:validate-xml:0.1.0}OrderService",
		"content":"org.switchyard.HandlerException: Validator 'org.switchyard.validate.xml.internal.XmlValidator' failed: 1 validation error(s): \norg.xml.sax.SAXParseException: cvc-complex-type.2.4.d: Invalid content was found starting with element 'invalid-element'. No child element is expected at this point.\n",
		"context":[{"type":"Message"}],
		"unitId":"f6a571b7-896a-4514-a1fa-90742f65ee88",
		"unitIndex":1,
		"timestamp":1378282559394
	}],
	"origin":{"host":"gbrown-redhat","thread":"http-localhost.localdomain/127.0.0.1:8080-1","node":"gbrown-redhat"}
}]

Expected results:

The response should have the 'replyTo' id matching the request's message id.


Additional info:

Comment 2 JBoss JIRA Server 2013-09-06 14:37:30 UTC
Gary Brown <gary> updated the status of jira RTGOV-262 to Resolved

Comment 3 Jiri Pechanec 2013-09-24 15:06:52 UTC
Verified in ER3

Comment 7 JBoss JIRA Server 2014-07-02 09:19:16 UTC
Gary Brown <gary> updated the status of jira RTGOV-262 to Closed


Note You need to log in before you can comment on or make changes to this bug.