You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "manav (JIRA)" <ji...@apache.org> on 2007/03/15 13:53:34 UTC
[jira] Created: (AMQ-1207) Expired Message Listener
Expired Message Listener
------------------------
Key: AMQ-1207
URL: https://issues.apache.org/activemq/browse/AMQ-1207
Project: ActiveMQ
Issue Type: Sub-task
Components: Broker
Affects Versions: 4.1.0
Reporter: manav
Priority: Blocker
ActiveMQ 3.2.1 had expired message listeners where if a message from Destination1 is expired (after timeToLive) the message could be configured to be sent to org.activemq.deadletter.Destination1 automatically. We were using this feature in AMQ3.2.1 to identify expired messages and execute some logic when messages are expired.
However this feature is not available in AMQ4.1/AMQ4.1.1.
This needs to be fixed as well along with expiring messages properly in the code.
Is it possible to give a high priority to this fix and fix it in code on an expedited basis? AMQ is being used in our product and major insurance companies are using the product. It is definitly going to give high visibility to ActiveMQ if we continued to use AMQ. Refactoring the code to not use AMQ is our option if this issue is not going to be resolved which we are wanting to avoid by all means.
We would appreciate a Date for the resolution to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-1207) Expired Message Listener
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies resolved AMQ-1207.
-----------------------------
Resolution: Fixed
Fix Version/s: 5.0.0
Fixed by svn revision 558054
> Expired Message Listener
> ------------------------
>
> Key: AMQ-1207
> URL: https://issues.apache.org/activemq/browse/AMQ-1207
> Project: ActiveMQ
> Issue Type: Sub-task
> Components: Broker
> Affects Versions: 4.1.0
> Reporter: manav
> Assignee: Rob Davies
> Priority: Blocker
> Fix For: 5.0.0
>
>
> ActiveMQ 3.2.1 had expired message listeners where if a message from Destination1 is expired (after timeToLive) the message could be configured to be sent to org.activemq.deadletter.Destination1 automatically. We were using this feature in AMQ3.2.1 to identify expired messages and execute some logic when messages are expired.
> However this feature is not available in AMQ4.1/AMQ4.1.1.
> This needs to be fixed as well along with expiring messages properly in the code.
> Is it possible to give a high priority to this fix and fix it in code on an expedited basis? AMQ is being used in our product and major insurance companies are using the product. It is definitly going to give high visibility to ActiveMQ if we continued to use AMQ. Refactoring the code to not use AMQ is our option if this issue is not going to be resolved which we are wanting to avoid by all means.
> We would appreciate a Date for the resolution to this issue.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (AMQ-1207) Expired Message Listener
Posted by "Rob Davies (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Davies reassigned AMQ-1207:
-------------------------------
Assignee: Rob Davies
> Expired Message Listener
> ------------------------
>
> Key: AMQ-1207
> URL: https://issues.apache.org/activemq/browse/AMQ-1207
> Project: ActiveMQ
> Issue Type: Sub-task
> Components: Broker
> Affects Versions: 4.1.0
> Reporter: manav
> Assignee: Rob Davies
> Priority: Blocker
> Fix For: 5.0.0
>
>
> ActiveMQ 3.2.1 had expired message listeners where if a message from Destination1 is expired (after timeToLive) the message could be configured to be sent to org.activemq.deadletter.Destination1 automatically. We were using this feature in AMQ3.2.1 to identify expired messages and execute some logic when messages are expired.
> However this feature is not available in AMQ4.1/AMQ4.1.1.
> This needs to be fixed as well along with expiring messages properly in the code.
> Is it possible to give a high priority to this fix and fix it in code on an expedited basis? AMQ is being used in our product and major insurance companies are using the product. It is definitly going to give high visibility to ActiveMQ if we continued to use AMQ. Refactoring the code to not use AMQ is our option if this issue is not going to be resolved which we are wanting to avoid by all means.
> We would appreciate a Date for the resolution to this issue.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.