Bug 777714 (SOA-230)

Summary: ConnectionTable problem after a while in 2 node cluster
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Martin Vecera <mvecera>
Component: JBossASAssignee: Vladimir Blagojevic <vladimir.blagojevic>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.2 IR8   
Target Milestone: ---   
Target Release: 4.2 CP01   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-230
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Two physical machines both running RHEL5, Sun JVM 1.5.0_12, full SOA-P 4.2.0.IR8 based on EAP 4.3.0.GA (build: SVNTag=JBPAPP_4_3_0_GA date=200711291835), Orcale DB on a separate machine
Last Closed: 2007-12-20 13:39:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Martin Vecera 2007-12-13 10:29:46 UTC 
Date of First Response: 2007-12-13 10:29:53
project_key: SOA

Reproducible: 100%

1. I took full IR8 and used dbinstall (https://svn.corp.jboss.com/repos/soa/trunk/qa/dbinstall/) for the 'all' configuration to use Oracle DB.
2. I unsecured jmx-service-invoker.
3. I copied the SOA-P to the second node.
4. I changed the server peer id on the both copies to be different.
5. I started the first node, it was successful.
6. I started the second node successfully as well.
7. I let it be for half an hour.
8. This appeared in the log files:

Node 1:
2007-12-13 10:57:07,502 WARN [org.jgroups.blocks.ConnectionTable] peer closed connection, trying to re-send msg
2007-12-13 10:57:07,502 ERROR [org.jgroups.blocks.ConnectionTable] 2nd attempt to send data failed too

Node 2:
2007-12-13 10:57:08,927 WARN [org.jgroups.blocks.ConnectionTable] peer closed connection, trying to re-send msg
2007-12-13 10:57:08,928 ERROR [org.jgroups.blocks.ConnectionTable] 2nd attempt to send data failed too

It doesn't seem like there's anything related to the problems in the logs (no exceptions, no other JGroups related output...).
Comment 1 Martin Vecera 2007-12-13 10:30:30 UTC 
Link: Added: This issue incorporates JGRP-646
Comment 2 ryan.campbell 2007-12-13 15:29:53 UTC 
Phillip is going to recreate this and create a JBPAPP issue for it, and probably a JBMESSAGING bug.
Comment 3 Phillip Thurmond 2007-12-13 18:58:58 UTC 
I was unable to reproduce this in the performance lab.  I used the latest EAP 4.3 build and mysql as the messaging persistence db.  Martin, can you try to reproduce this in the QA lab?
Comment 4 Martin Vecera 2007-12-14 07:16:10 UTC 
I tried to reproduce it on our machines and it took 13 hours to happen. But it happened! I'll give it a try in the QA lab...
Comment 5 Martin Vecera 2007-12-20 13:38:24 UTC 
I tried to reproduce it in QA lab on machines cluster09 & 10 with MySQL database on perfdb01 and I was not able to reproduce the problem. Maybe it was a local network issue. I'm going to close the issue for now...