[
https://issues.apache.org/jira/browse/ARTEMIS-2654?focusedWorklogId=402175&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-402175
]
ASF GitHub Bot logged work on ARTEMIS-2654:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Mar/20 13:58
Start Date: 12/Mar/20 13:58
Worklog Time Spent: 10m
Work Description: michaelpearce-gain commented on issue #3015:
ARTEMIS-2654 Improving Page cleanup and Operation Context
URL: https://github.com/apache/activemq-artemis/pull/3015#issuecomment-598200164
Just watching logs like a hawk atm whilst testing this, we're not using
large messages, and likewise there is no ids, but with master + this pr, i see
in the logs the below, which is spurious (i dont think its this PR, but
something to check - and maybe fix, not sure what introduced it)
2020-03-12 13:54:30,271 INFO [org.apache.activemq.artemis.core.server]
AMQ224100: Timed out waiting for large messages deletion with IDs [], might not
be deleted if broker crashes atm
2020-03-12 13:54:35,272 INFO [org.apache.activemq.artemis.core.server]
AMQ224100: Timed out waiting for large messages deletion with IDs [], might not
be deleted if broker crashes atm
----------------------------------------------------------------
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: 402175)
Time Spent: 1h 40m (was: 1.5h)
> Improve Paging.Stop cleanup
> ---------------------------
>
> Key: ARTEMIS-2654
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2654
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.11.0
> Reporter: Clebert Suconic
> Priority: Major
> Fix For: 2.12.0
>
> Time Spent: 1h 40m
> Remaining Estimate: 0h
>
> There's a Blocking operation on Page.stopPaging and cleanup should use its
> own OperationContext.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)