[
http://jira.jboss.com/jira/browse/JBSEAM-3084?page=all ]
Pete Muir closed JBSEAM-3084.
-----------------------------
Resolution: Rejected
Sorry, I fail to see where any exception is swallowed in the AsynchronousInterceptor.
You are correct, async exeptions *do* get swallowed in some cases (e.g. when using the EJB
timer) however not by Seam, but by the underlying timer implementation.
AsynchronousInterceptor swallows any exception thrown
-----------------------------------------------------
Key: JBSEAM-3084
URL:
http://jira.jboss.com/jira/browse/JBSEAM-3084
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.0.A1
Reporter: Dan Allen
Assigned To: Dan Allen
Fix For: 2.1.0.BETA1
Attachments: JBSEAM-3084-v1.txt
Original Estimate: 15 minutes
Remaining Estimate: 15 minutes
The AsynchronousInterceptor swallows any exception thrown. I expect that it would at the
very least log the exception using the error level so there is some indication that it
happened.
Here is a snippet of the interceptor code under question.
try
{
return invocation.proceed();
}
finally { ... }
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira