Bug 984849

Summary: Runtime and checked exceptions are handled differently from auditors POV
Product: [JBoss] JBoss Fuse Service Works 6 Reporter: Jiri Pechanec <jpechane>
Component: SwitchYardAssignee: Keith Babo <kbabo>
Status: CLOSED NOTABUG QA Contact: Jiri Sedlacek <jsedlace>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: oskutka, soa-p-jira
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-22 17:01:05 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:
Attachments:
Description Flags
Reproducer none

Description Jiri Pechanec 2013-07-16 07:48:24 UTC 
When a checked exception is thrown then it is handled by provider processor but when runtime exception is thrown it is handled by error processor. This can lead into different behaviour and introduce hard-to-find bugs.

An example is attached - see test OrderServiceTest. A service is called twice once throwing checked and once unchecked exception.

Diff files f1.txt and f2.txt in reproducer to see that different processors are in place.
Comment 1 Jiri Pechanec 2013-07-16 07:49:02 UTC 
Created attachment 774055 [details]
Reproducer
Comment 2 Keith Babo 2013-08-02 14:37:58 UTC 
The internal handling of these exceptions is different, so I would expect the audit behavior to be different as well.  Auditors are intended as low-level debugging tools and are tightly integrated with the bus behavior in SY.  User applications should use these sparingly and should not use them at all to influence runtime behavior.  ExchangeInterceptors, on the other hand, should be very predictable and can be used by end users in both test and runtime.