[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-642) Cause exceptions in DLQHandler are not logged

Tue Apr 8 13:15:59 EDT 2008

     [ http://jira.jboss.com/jira/browse/EJBTHREE-642?page=all ]

Galder Zamarreno updated EJBTHREE-642:
--------------------------------------

    Priority: Minor  (was: Major)

> Cause exceptions in DLQHandler are not logged
> ---------------------------------------------
>
>                 Key: EJBTHREE-642
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-642
>             Project: EJB 3.0
>          Issue Type: Bug
>    Affects Versions: EJB 3.0 RC7 - FD
>            Reporter: Galder Zamarreno
>         Assigned To: Galder Zamarreno
>            Priority: Minor
>
> I am trying to debug a customer problem and while trying to replicate it, I have 
> found that exception logging in the MDB is not clear enough.
> Basically, I'm getting an exception in DQLHandler.createService() which is not a JMSException. 
> When the exception is logged in MDB.onException(), it does not show the original exception 
> (original exceptions message is null) which forces me to actually debug the EJB3 code in 
> order to find out what exactly is wrong with it.
> I guess you might wanna override the Exception(Throwable) constructor in JMSException so that
> you can pass the cause exception and thus, get log4j to print the original exception.

-- 
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