[
https://issues.apache.org/activemq/browse/AMQ-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rob Davies resolved AMQ-1517.
-----------------------------
Resolution: Fixed
Added a sendTimeout property to MessageProducer that can also be set via a
Connection/ConnectionFactory for all producers
by SVN revision 646437
> Support for more graceful handling of timeouts within MessageProducer.send
> --------------------------------------------------------------------------
>
> Key: AMQ-1517
> URL: https://issues.apache.org/activemq/browse/AMQ-1517
> Project: ActiveMQ
> Issue Type: New Feature
> Components: JMS client
> Affects Versions: 5.0.0
> Reporter: Rob Davies
> Assignee: Rob Davies
> Fix For: 5.1.0
>
>
> We are using queue limits with a SEDA style architecture. We have certain
> queues which are machine specific in our storage solution so if the storage
> machine was to crash for whatever reason there is the possibility that our
> failure detection could happen after we have filled the queue up meaning we
> have deadlocked our workflow. It would be nice if we could put a timeout on a
> MessageProducer.send();
> The desired behavior for sending when queue limits are reached would be able
> to configure a producer to do any of the following three things:
> 1. Block until under the queue limit. This is current behavior.
> 2. Have a timeout value.
> 3. Throw an exception immediately.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
