Bug 1090675 - Two nodes with different multicast adress recognize each other
Summary: Two nodes with different multicast adress recognize each other
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Portal
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER02
: 6.2.0
Assignee: Lucas Ponce
QA Contact: vramik
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-23 22:47 UTC by vramik
Modified: 2014-07-01 02:36 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker GTNPORTAL-3457 0 Major Resolved Unify gatein jgroups configurations 2016-12-19 12:17:18 UTC

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


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