activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Gellings (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-247) Bug in FutureResponse on how handles timeout
Date Mon, 26 Apr 2010 14:19:28 GMT

    [ https://issues.apache.org/activemq/browse/AMQNET-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59100#action_59100
] 

Mark Gellings commented on AMQNET-247:
--------------------------------------

To add.  We ended up disabling producer flow control on broker topics and increasing the system
usage memory on the broker.  During stress testing of Queues we didn't run into this problem
so we left flow control on for queues.

> 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.


Mime
View raw message