[ 
https://issues.apache.org/jira/browse/ARTEMIS-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18056261#comment-18056261
 ] 

ASF subversion and git services commented on ARTEMIS-5861:
----------------------------------------------------------

Commit 175d32d6e584e2d502ab666a808a4d1f9af3cd8e in artemis's branch 
refs/heads/main from Justin Bertram
[ https://gitbox.apache.org/repos/asf?p=artemis.git;h=175d32d6e5 ]

ARTEMIS-5861 fix doc & test issue

This commit also increases the DEFAULT_SHUTDOWN_TIMEOUT used on the
test-suite from 0 to 7200000 (i.e. 2 hours) in order to ensure the
timeout code is exercised and to expose any issues with closing the
Netty ChannelGroups or EventLoopGroup.


> 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: 3.5h
>  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]

Reply via email to