You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/01/27 02:37:00 UTC
[jira] [Work logged] (ARTEMIS-2240) ActiveMQThreadPoolExecutor
should use LinkedTransferQueue
[ https://issues.apache.org/jira/browse/ARTEMIS-2240?focusedWorklogId=190480&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-190480 ]
ASF GitHub Bot logged work on ARTEMIS-2240:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 27/Jan/19 02:36
Start Date: 27/Jan/19 02:36
Worklog Time Spent: 10m
Work Description: franz1981 commented on pull request #2524: ARTEMIS-2240 ActiveMQThreadPoolExecutor should use LinkedTransferQueue
URL: https://github.com/apache/activemq-artemis/pull/2524
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 190480)
Time Spent: 10m
Remaining Estimate: 0h
> ActiveMQThreadPoolExecutor should use LinkedTransferQueue
> ---------------------------------------------------------
>
> Key: ARTEMIS-2240
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2240
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> ActiveMQThreadPoolExecutor should use LinkedTransferQueue to reduce cost over contention, given that internally it isn't using ReentrantLock as LinkedBlockingQueue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)