[
https://issues.apache.org/jira/browse/ARTEMIS-2002?focusedWorklogId=262838&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-262838
]
ASF GitHub Bot logged work on ARTEMIS-2002:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 19/Jun/19 07:33
Start Date: 19/Jun/19 07:33
Worklog Time Spent: 10m
Work Description: franz1981 commented on pull request #2707: ARTEMIS-2002
Proton transport objects leaked
URL: https://github.com/apache/activemq-artemis/pull/2707#discussion_r295156216
##########
File path:
artemis-protocols/artemis-amqp-protocol/src/main/java/org/apache/activemq/artemis/protocol/amqp/proton/AMQPConnectionContext.java
##########
@@ -183,6 +191,17 @@ public void flush() {
}
public void close(ErrorCondition errorCondition) {
+ synchronized (schedulingLock) {
+ isSchedulingCancelled = true;
+
+ if (scheduledPool != null && scheduledPool instanceof
ThreadPoolExecutor &&
+ scheduledFuture != null && scheduledFuture instanceof Runnable) {
+ if (!((ThreadPoolExecutor) scheduledPool).remove((Runnable)
scheduledFuture)) {
Review comment:
Yep, but the resources that can actually lead to OOM are not the Runnable,
but the context that the Runnable(s) contains: If such context is referenced in
an explicit, but `WeakReference` it would allow it to be collected when
deferenced elsewhere.
Then the leaking `Runnable`s will be removed on the next (supposed) fire,
without affecting scalability.
The memory consumption of a Runnable without any context is ~64 bytes so it
is very unlikely to be the cause of OOM per se.
----------------------------------------------------------------
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: 262838)
Time Spent: 2h 40m (was: 2.5h)
> Proton transport objects leaked if client disconnects abruptly leading to
> OutOfMemoryError: Java heap space
> -----------------------------------------------------------------------------------------------------------
>
> Key: ARTEMIS-2002
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2002
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 2.6.2
> Reporter: Keith Wall
> Priority: Major
> Attachments: ARTEMIS-2002-OOMEHeap-ProtonObjectsLeaked.png
>
> Time Spent: 2h 40m
> Remaining Estimate: 0h
>
> If an AMQP client with an attached receiving link disconnects abruptly (i.e.
> closes socket without sending the AMQP close performative), {{TransportImpl}}
> and other Proton class instances remain referenced within the heap. If many
> such clients do this, an OutOfMemoryError: Java heap space occurs. This
> occurs even though the underlying socket connection has been closed.
> I have reproduced this issue against both 2.6.2 and master
> (f0c13622ac7e821a81a354b0242ef5235b6e82df).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
