activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (AMQ-751) Extend ExceptionListener mechanism by creating a custom AMQ exception which would provide more detail about the exception
Date Sun, 25 Sep 2011 16:58:26 GMT

     [ https://issues.apache.org/jira/browse/AMQ-751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Timothy Bish closed AMQ-751.
----------------------------

    Resolution: Won't Fix

> Extend ExceptionListener mechanism by creating a custom AMQ exception which would provide
more detail about the exception
> -------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-751
>                 URL: https://issues.apache.org/jira/browse/AMQ-751
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker, JMS client
>            Reporter: Massive Boisson
>            Priority: Minor
>             Fix For: AGING_TO_DIE
>
>
> To quote James:
> "I wonder if we could add a neater non-JMS extension to ActiveMQ to make it easier to
be notified asynchronously of which Message objects could not be sent? I guess we could just
use the ExceptionListener and use a custom type of Exception which contained the Message object?"
> I think this would greatly increase the usefulness of async sends.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message