[
https://issues.apache.org/jira/browse/ARTEMIS-2513?focusedWorklogId=325683&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-325683
]
ASF GitHub Bot logged work on ARTEMIS-2513:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 09/Oct/19 13:18
Start Date: 09/Oct/19 13:18
Worklog Time Spent: 10m
Work Description: gaohoward commented on issue #2859: ARTEMIS-2513 Large
message's copy may be interfered by other threads
URL: https://github.com/apache/activemq-artemis/pull/2859#issuecomment-539996782
pls hold this, it's getting test failures in jenkins.
----------------------------------------------------------------
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: 325683)
Time Spent: 20m (was: 10m)
> Large message's copy may be interfered by other threads
> -------------------------------------------------------
>
> Key: ARTEMIS-2513
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2513
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: Broker
> Affects Versions: 2.10.1
> Reporter: Howard Gao
> Assignee: Howard Gao
> Priority: Major
> Fix For: 2.11.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> In LargeMessageImpl.copy(long) it need to open the underlying file in order
> to read and copy bytes into the new copied message. However there is a chance
> that another thread can come in and close the file in the middle, making the
> copy failed with "channel is null" error.
> This is happening in cases where a large message is sent to a jms topic
> (multicast address). During delivery it to multiple subscribers, some
> consumer is doing delivery and closed the underlying file after. Some other
> consumer is rolling back the messages and eventually move it to DLQ (which
> will call the above copy method). So there is a chance this bug being hit on.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
