[
https://issues.apache.org/activemq/browse/AMQNET-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58731#action_58731
]
Mark Gellings commented on AMQNET-247:
--------------------------------------
I also believe the catch block should rethrow the exception as follows:
try
{
if(!latch.await(maxWait))
{
// TODO: Throw timeout exception?
}
}
catch (Exception e)
{
Tracer.Error("Caught while waiting on monitor: " + e);
throw;
}
> Bug in FutureResponse on how handles timeout
> --------------------------------------------
>
> Key: AMQNET-247
> URL: https://issues.apache.org/activemq/browse/AMQNET-247
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: NMS
> Affects Versions: 1.2.0
> Reporter: Mark Gellings
> Assignee: Jim Gomes
>
> In FutureReponse.cs, in the Response getter if !latch.awaite(maxWait) times
> out a timeout exception should be thrown. Currently there is just a TODO
> comment.
> This is a bug because when it is not thrown the producer thinks the message
> was sent successfully when actually it wasn't. This could be problematic to
> any system if a message really isn't sent.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
