Bug 1603973 - [GSS](6.4.z) HornetQ cannot failover with network disconnected
Summary: [GSS](6.4.z) HornetQ cannot failover with network disconnected
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: HornetQ
Version: 6.4.21
Hardware: All
OS: Linux
high
unspecified
Target Milestone: CR1
: EAP 6.4.21
Assignee: jboss-set
QA Contact: Peter Mackay
URL:
Whiteboard:
Depends On:
Blocks: eap6421-payload 1610346 1610355
TreeView+ depends on / blocked
 
Reported: 2018-07-19 19:44 UTC by Clebert Suconic
Modified: 2021-12-10 16:43 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:42:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-15273 0 Major New [GSS](7.1.z) ARTEMIS-2038 - Artemis cannot failover with network disconnected 2018-10-19 20:01:25 UTC

Description Clebert Suconic 2018-07-19 19:44:46 UTC
Description of problem:

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.

Actual results:

Connection writer hangs forever, Pinger can't disconnect connection.

Expected results:

Connection failure or retry happening regularly.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.