[
https://issues.apache.org/jira/browse/QPID-7237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15280265#comment-15280265
]
ASF subversion and git services commented on QPID-7237:
-------------------------------------------------------
Commit 1743387 from [email protected] in branch 'java/branches/6.0.x'
[ https://svn.apache.org/r1743387 ]
QPID-7237: [Java Client] Use single thread thread-pool to perform flow control
on no-ack sessions
* Avoids spawning new thread for each state change
* Coalesce flow control tasks for no-ack sessions
* Change the lower prefetch threshold to be half of upper prefetch threshold
when the same values for thresholds are specified
merged from trunk using
svn merge -c 1742900,1743383 ^/qpid/java/trunk
> Excessive threads creation when suspending/resuming flow
> --------------------------------------------------------
>
> Key: QPID-7237
> URL: https://issues.apache.org/jira/browse/QPID-7237
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Affects Versions: 0.24, qpid-java-6.0.2
> Reporter: Flavio Baronti
> Assignee: Keith Wall
> Fix For: qpid-java-6.0.3, qpid-java-6.1
>
> Attachments: QPID-7237.patch
>
>
> In high load situations, with a NO_ACKNOWLEDGE session, it is possible for
> the client to create an excessive amount of threads to suspend/resume the
> channel.
> I'm providing a patch to avoid creating a new thread if the previous thread
> has not completed its operation. This patch appears to avoid the problem in
> our environment. Notice we are using version 0.24, but the code is the same
> in the latest version.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
