You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2015/06/11 14:23:00 UTC
[jira] [Commented] (QPID-6583) [Java Client] AMQSession_0_10 should
use connection task pool rather than a Timer
[ https://issues.apache.org/jira/browse/QPID-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14581877#comment-14581877 ]
ASF subversion and git services commented on QPID-6583:
-------------------------------------------------------
Commit 1684863 from [~godfrer] in branch 'java/trunk'
[ https://svn.apache.org/r1684863 ]
QPID-6583 : [Java Client] AMQSession_0_10 should use connection task pool rather than a Timer
> [Java Client] AMQSession_0_10 should use connection task pool rather than a Timer
> ---------------------------------------------------------------------------------
>
> Key: QPID-6583
> URL: https://issues.apache.org/jira/browse/QPID-6583
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Rob Godfrey
> Assignee: Rob Godfrey
> Fix For: 6.0 [Java]
>
>
> Currently the AMQSession_0_10 class uses a static time object to schedule ack flushing. This leaves a thread running at all times even if all connections are closed.
> In preference to this we can use the thread pool already associated with the connection to run the tasks currently run on the timer.
> See [this mail|http://mail-archives.apache.org/mod_mbox/qpid-users/201506.mbox/%3CCAJ2jEUtdc8mUV45Rm6XoZpj_1ZPo3n1R7GG4X%3DQtiy%2BoRbSfWw%40mail.gmail.com%3E] for the issues that the current mechanism may cause.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org