[
https://issues.apache.org/jira/browse/ARTEMIS-5861?focusedWorklogId=1003310&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1003310
]
ASF GitHub Bot logged work on ARTEMIS-5861:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Feb/26 16:05
Start Date: 03/Feb/26 16:05
Worklog Time Spent: 10m
Work Description: clebertsuconic commented on PR #6202:
URL: https://github.com/apache/artemis/pull/6202#issuecomment-3842207535
@jbertram can you add an explanation on the comments for the large timeout..
on why we are doing that?
Or if you don't like to add it there, add the explanation on the commit
message.. so if someone ever wonder why this timeout is that large, they can
read the comment on either the commit or on the code..
or do both :) ... just wanted to have this information somewhere in the
commit and code
Issue Time Tracking
-------------------
Worklog Id: (was: 1003310)
Time Spent: 3h (was: 2h 50m)
> Netty acceptor not shutting down
> --------------------------------
>
> Key: ARTEMIS-5861
> URL: https://issues.apache.org/jira/browse/ARTEMIS-5861
> Project: Artemis
> Issue Type: Bug
> Affects Versions: 2.44.0
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Labels: pull-request-available
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Thread dump analysis reveals that the broker hangs indefinitely when trying
> to close Netty channel groups in a Netty acceptor, e.g.:
> {noformat}
> State: WAITING (on object monitor)
> Stack trace:
> at
> io.netty.util.concurrent.DefaultPromise.awaitUninterruptibly(DefaultPromise.java:290)
> - locked <0x00000000dbd095a8> (a
> io.netty.channel.group.DefaultChannelGroupFuture)
> at
> io.netty.channel.group.DefaultChannelGroupFuture.awaitUninterruptibly(DefaultChannelGroupFuture.java:178)
> at
> org.apache.activemq.artemis.core.remoting.impl.netty.NettyAcceptor.asyncStop(NettyAcceptor.java:793){noformat}
>
> The code at {{NettyAcceptor.java:793}} calls
> {{channelGroup.close().awaitUninterruptibly()}} without a timeout parameter
> causing indefinite hang when channels fail to close properly. This problem is
> very rare and there is no good reproducer
> The broker should complete shutdown within a reasonable timeout period,
> forcefully closing any remaining connections if necessary.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
