[
https://issues.apache.org/activemq/browse/AMQNET-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59099#action_59099
]
Mark Gellings commented on AMQNET-247:
--------------------------------------
In my opinion I think the implementation should be the same as the java
implementation, so no Exception. Although I know the implementations between
NMS and the java client will drift a bit as needed due to the language
semantics.
I would focus our effort on the producer window size since that seems to be the
true fix for this.
> 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.
