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

ASF GitHub Bot logged work on ARTEMIS-5861:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 30/Jan/26 17:53
            Start Date: 30/Jan/26 17:53
    Worklog Time Spent: 10m 
      Work Description: gemmellr commented on PR #6202:
URL: https://github.com/apache/artemis/pull/6202#issuecomment-3824935000

   Garys idea seems reasonable, in some respects it is a bit weird to warn 
about something not happening yet, when being explicitly instructed not to wait 
for it to happen. Could possibly drop it to info level if feeling strongly that 
it should still be noted, though its not clear why _this_ bit would be noted 
when it seems the existing usage of that config wasnt causing any warnings.
   
   That said, I also dont actually know that we really want this set to 0 all 
the time in the test suite? Until yesterday the related bit previously waited 
for as long as needed during the entire test suite, and now because of reusing 
an existing configuration value it will never wait at all. Feels a bit weird.




Issue Time Tracking
-------------------

    Worklog Id:     (was: 1002717)
    Time Spent: 1h 50m  (was: 1h 40m)

> 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: 1h 50m
>  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