[jboss-jira] [JBoss JIRA] (AS7-5497) Exception handling of EJB container for MDB is incorrect

[RH Bugzilla Integration (JIRA)]

    [ https://issues.jboss.org/browse/AS7-5497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763933#comment-12763933 ] 

RH Bugzilla Integration commented on AS7-5497:
----------------------------------------------

Jan Martiska <jmartisk at redhat.com> made a comment on [bug 900803|https://bugzilla.redhat.com/show_bug.cgi?id=900803]

verified in 6.1.0.ER3
                
> Exception handling of EJB container for MDB is incorrect
> --------------------------------------------------------
>
>                 Key: AS7-5497
>                 URL: https://issues.jboss.org/browse/AS7-5497
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 7.1.2.Final (EAP)
>         Environment: JBoss EAP 6.0.0
>            Reporter: Adam Kovari
>            Assignee: JBoss SET
>            Priority: Minor
>              Labels: eap6, ejb3.1
>             Fix For: EAP 6.1.0.Alpha (7.2.0.Final), 7.1.4.Final (EAP)
>
>
> After deploying a MDB with Container-Managed transaction and
> TransactionAttribute NOT_SUPPORTED, a RuntimeException thrown from
> within the MDB onMessage() is reported to the Adapter as such, with no
> EJBException wrapping. I.e.: the "((javax.jms.MessageListener)
> endPoint).onMessage(message)" call in our adapter fails with the
> exception type originally thrown.
> This does not look compliant with EJB 3.1 spec(JSR 318: Enterprise
> JavaBeansTM, Version 3.1, Table 20 page 392, last cell bottom right):
> "Throw EJBException that wraps the original exception to resource
> adapter".
> Another part of spec I was just made aware of says this:
> p383 of the spec states -
> In the case of a message-driven bean, the container logs the exception and then throws a javax.ejb.EJBException that wraps the original exception to the resource adapter. (See [15]).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira