Bug 1090675

Summary:	Two nodes with different multicast adress recognize each other
Product:	[JBoss] JBoss Enterprise Portal Platform 6	Reporter:	vramik
Component:	Portal	Assignee:	Lucas Ponce <lponce>
Status:	VERIFIED ---	QA Contact:	vramik
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	epp-bugs, lponce, ppalaga, tkyjovsk
Target Milestone:	ER02
Target Release:	6.2.0
Hardware:	Unspecified
OS:	Unspecified
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:

Description vramik 2014-04-23 22:47:42 UTC

Description of problem:
When you start two portals on one machine (I use -Djboss.socket.binding.port-offset=100 to avoid port conflict) and each of them has unique multicast adress recognize each other. 

Steps to Reproduce:
1. Start h2: java -cp modules/system/layers/base/com/h2database/h2/main/h2-1.3.168-redhat-2.jar org.h2.tools.Server
2. start first node: sh standalone.sh -c standalone-ha.xml -u 239.255.19.40
3. start second node: sh standalone.sh  -c standalone-ha.xml -Djboss.socket.binding.port-offset=100 -u 239.255.19.43

Actual results:
Nodes recognize each other

Expected results:
Nodes won't be able to recognize the other.

Additional info:
In portal 6.1.1 everything works as expected.

Comment 2 Peter Palaga 2014-05-30 07:54:49 UTC

https://github.com/gatein/gatein-portal/pull/842 was merged in upstream on  2014-04-25 and the fix reached JBoss Portal 6.2.0 ER2. Setting status directly to ON_QA