[
https://issues.apache.org/jira/browse/ARTEMIS-2434?focusedWorklogId=283481&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-283481
]
ASF GitHub Bot logged work on ARTEMIS-2434:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 26/Jul/19 17:00
Start Date: 26/Jul/19 17:00
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on issue #2771: ARTEMIS-2434
Don't lock ServerConsumerImpl for long period of time
URL: https://github.com/apache/activemq-artemis/pull/2771#issuecomment-515527535
If you can change the commit message to reflect what you are really doing
here..
you are retrying the locks in a loop... I don't know what message though :)
but can you find something more in line to what you're doing?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 283481)
Time Spent: 0.5h (was: 20m)
> Don't lock ServerConsumerImpl for long period of time
> -----------------------------------------------------
>
> Key: ARTEMIS-2434
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2434
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Affects Versions: 2.9.0
> Reporter: Francesco Nigro
> Priority: Major
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> ServerConsumerImpl::lockDelivery is always being called while holding the
> ServerConsumerImpl::lock and it would prevent ServerConsumerImpl::handle to
> proceed, making afterAck/afterRollback operations unable to acquire the
> QueueImpl monitor, holded while awating ServerConsumerImpl::handle.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
