[jira] [Closed] (ARTEMIS-2038) Artemis cannot failover with network disconnected

["Clebert Suconic (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ARTEMIS-2038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic closed ARTEMIS-2038.
------------------------------------
    Resolution: Abandoned

this was fixed by moving into a  newer version of Netty that allows NIO. 


I would close it as Out-of-date but there's no such Resolution status in this JIRA instance.


So, closing this one as it's not an issue any longer.

> Artemis cannot failover with network disconnected
> -------------------------------------------------
>
>                 Key: ARTEMIS-2038
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2038
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 1.5.5
>            Reporter: Brad Maxwell
>            Priority: Major
>
> HornetQ is using Netty 3 with OIO, which is using BlockedIO, which is basically an SocketOutputStream.
> There is an issue with disconnecting the cable or disabling network, in which the writer will lock the Pinger, Pinger will not be able to cleanup the connection.
> Notice this not apply to Artemis which is 100 non blocking, so I'm not sure these fixes will be applied upstream in Artemis.
> Version-Release number of selected component (if applicable):
> How reproducible:
> 100% reproduceable.
> Steps to Reproduce:
> 1. Have a producer connection so much that it flow control the server. (disable flow control for easier reproducing)
> 2. Disconnect network (ifconfig down or pull of cable)
> or:
> 1. I have developed NettyManualFailoverTest which will be part of the fix. follow the steps of the test and it will show the issue.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)