Bug 1056216 – [GSS] (6.3.0) Change initial connection behavior for cluster connection

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1056216 - [GSS] (6.3.0) Change initial connection behavior for cluster connection

Summary:	[GSS] (6.3.0) Change initial connection behavior for cluster connection

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	HornetQ (Show other bugs)
Sub Component:
Version:	6.2.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	DR2
Target Release:	EAP 6.3.0
Assigned To:	Justin Bertram
QA Contact:	Miroslav Novak
Docs Contact:	Russell Dickenson

URL:
Whiteboard:
Keywords:

Depends On:	1057330 1064596
Blocks:	1087632
	Show dependency tree / graph

Reported:	2014-01-21 12:21 EST by Justin Bertram
Modified:	2014-08-11 22:08 EDT (History)
CC List:	6 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:	If a clustered HornetQ instance lost its connection to other cluster nodes, reconnection attempts could result in an infinite loop. For a static cluster configuration, any initial connect attempt would be attempted infinitely, ignoring the `reconnect-attempts` parameter. For a dynamic cluster configuration, if the node was disconnected between the time it received a notification about the node being part of the cluster topology and the initial connection, reconnection attempts continued infinitely. This issue has been resolved and the clustering logic now uses the `reconnect-attempts` parameter for both the initial connection attempts and reconnection attempts.
Story Points:	---
Clone Of:
Clones:	1087632 (view as bug list)
Environment:
Last Closed:	2014-08-06 10:36:28 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Justin Bertram 2014-01-21 12:21:03 EST

Cluster connection bridge should use the "reconnect-attempts" value for both the initial connection attempts and reconnection attempts.

Comment 1 Justin Bertram 2014-01-21 14:25:55 EST

Fix committed to the 2.3.x branch.  See https://github.com/hornetq/hornetq/commit/8ef706763c784aebc43c1b4aa3dfc309122f5f2d.

Comment 2 Kabir Khan 2014-04-04 10:46:11 EDT

Setting to ON_QA since upgrade should fix this

Comment 3 Miroslav Novak 2014-05-05 10:05:35 EDT

Hi,

do we have a way to reproduce this issue. I did some tries with debugger but without success. Can you help, please?

Thanks,
Mirek

Comment 4 Shaun Appleton 2014-05-05 17:04:22 EDT

It can't easily be produced without a debugger https://issues.jboss.org/browse/HORNETQ-1306 provides the steps.

Comment 5 Miroslav Novak 2014-05-06 04:46:49 EDT

Thanks Shaun! I'll give it a try.

Comment 6 Miroslav Novak 2014-05-06 07:12:44 EDT

Fix is not present in HornetQ tag HornetQ_2_3_18_Final which is in EAP 6.3.0.ER3. (It seems that it was merged just to master but not to 2.3.x branch.)

This fix also requires update of xsd schema so attribute "initial-connect-attempts" can be set in standalone...xml and domain.xml.

Comment 7 Miroslav Novak 2014-05-07 06:27:52 EDT

Ignore my comment above. Attribute "reconnect-attempts" defines initial retry. I've managed to reproduce the issue and don't see the described problem again when "reconnect-attempts" is set to 3 in cluster-connections.

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