Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1175722

Summary: [GSS](6.4.z) Add WARN log when setting connection-ttl OR connection-ttl-override equal to check-period
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Matthew Robson <mrobson>
Component: HornetQAssignee: Ryan Emerson <remerson>
Status: CLOSED CURRENTRELEASE QA Contact: Miroslav Novak <mnovak>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: bmaxwell, cdewolf, istudens, msvehla, okalman, remerson, rpelisse
Target Milestone: CR1   
Target Release: EAP 6.4.5   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1235745, 1247277    

Description Matthew Robson 2014-12-18 13:28:56 UTC 
Description of problem:
If connection ttl is equal to the check-period there is only 1 opportunity to validate the live / backup connection, cluster connection or replication connection.  If a system is under highload or there is a minor network delay there is a high probability of a clister split / failure due to connection timeout. 

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Set connection-ttl or override to 30000ms and check-period to 30000 (default)
2. Add 500ms of latency to the network interface:
tc qdisc add dev lo root handle 1:0 netem delay 500msec
3. Cluster will split

Actual results:
Cluster splits causing more then 1 live server in a live / backup pair.

Expected results:
Add a WARN log recommending not setting connection-ttl / override to the same value as the check-period for the reasons noted above.

Additional info:
Comment 3 JBoss JIRA Server 2015-06-25 13:19:41 UTC 
Ryan Emerson <remerson> updated the status of jira HORNETQ-1482 to Coding In Progress
Comment 7 JBoss JIRA Server 2015-07-03 09:23:09 UTC 
Ryan Emerson <remerson> updated the status of jira HORNETQ-1482 to Resolved
Comment 8 Ryan Emerson 2015-07-09 16:00:09 UTC 
2.3.x PR: https://github.com/hornetq/hornetq/pull/2033
Comment 9 Ryan Emerson 2015-07-09 16:26:00 UTC 
2.3.25.x Commit: https://github.com/hornetq/hornetq/commit/20f9edd17b5673e94b24953295c54c71f319f190
Comment 10 Ondřej Kalman 2015-08-03 09:25:25 UTC 
Hi, we need to make this fix also for EAP/wildfly not only for standalone broker. 
parseMainConfig() method is never called when EAP is starting
Comment 12 JBoss JIRA Server 2015-08-05 08:49:20 UTC 
Ryan Emerson <remerson> updated the status of jira HORNETQ-1482 to Reopened
Comment 19 JBoss JIRA Server 2015-09-16 09:05:57 UTC 
Ryan Emerson <remerson> updated the status of jira HORNETQ-1482 to Resolved
Comment 20 Ondřej Kalman 2015-11-03 10:33:42 UTC 
Verified with 6.4.5.CP.CR1
Comment 21 Petr Penicka 2017-01-17 11:42:10 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.
Comment 22 Petr Penicka 2017-01-17 11:42:51 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.