activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arthur Naseef (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-3875) Client / NetworkBridge Connection blocks all communication at the transport when producer-flow-control reached
Date Fri, 07 Dec 2012 17:07:21 GMT

    [ https://issues.apache.org/jira/browse/AMQ-3875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526545#comment-13526545
] 

Arthur Naseef commented on AMQ-3875:
------------------------------------

Do you mean for NON-PERSISTENT, non-transacted and NON-PERSISTENT transacted?

If so, the changes to the existing test case should be simple enough, right?

                
> Client / NetworkBridge Connection blocks all communication at the transport when producer-flow-control
reached
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3875
>                 URL: https://issues.apache.org/jira/browse/AMQ-3875
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.4.2
>            Reporter: Arthur Naseef
>         Attachments: TestProducerFlowControl.java
>
>
> When producer-flow-control throttles a producer, the entire connection for the client,
or network bridge, can be blocked until space clears.
> A unit test will be attached that demonstrates this situation with any of the following
types of messaging:
> * PERSISTENT, transacted
> * NON-PERSISTENT, non-transacted
> * NON-PERSISTENT, transacted
> PERSISTENT, non-transacted messages don't have this problem.  Internally, it seems that
any time messages are sent asynchronously across the transport (i.e. isResponseRequired()
== false), the problem occurs.
> The expected operation is for producers to the destination to block on send() and all
other operations across the same connection to continue normally.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message