[
https://issues.apache.org/activemq/browse/SM-872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_38719
]
Arjen Wiersma commented on SM-872:
----------------------------------
Response from gnodet:
Good point.
I'm not sure about removing the exchange if the client goes down,
because it would require to be able to make the difference
between such a scenario and when a node in the cluster goes down.
I'd rather use the timeout and discard the exchange if the timeout has been
exceeded when the exchange is about to be accepted.
Could you raise a JIRA please ?
> Expiring in-queue messages
> --------------------------
>
> Key: SM-872
> URL: https://issues.apache.org/activemq/browse/SM-872
> Project: ServiceMix
> Issue Type: Improvement
> Components: servicemix-jbi
> Affects Versions: 3.1
> Reporter: Arjen Wiersma
>
> While testing some scenarios with my freshly implemented JBI components I
> noticed something... if a client sends a message with a timeout set at say 10
> seconds, if the timeout expires it will get the expected TimeoutException.
> However the actual message remains in the queues and the result of the
> message is routed back to the message broker. If a client disconnects, the
> message is in the queue until I purge it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
