October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JGRP-130) Problems with reincarnation

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-130?page=all ] Bela Ban updated JGRP-130: -------------------------- Fix Version/s: 2.5.2 Needs to be backported to 2.5.2 > Problems with reincarnation > --------------------------- > > Key: JGRP-130 > URL: http://jira.jboss.com/jira/browse/JGRP-130 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.9 > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.6, 2.5.2 > > Attachments: tcp.xml > > > Problems with reincarnation > =========================== > Author: Bela Ban > Version: $Id$ > The identity of a JGroups member is always the IP address and a port. The port is usually chosen by the OS, unless > bind_port is set (not set by default). > Let's say a member's address is hostA:5000. When that member dies and is restarted, the OS will likely assign a > higher port, say 5002. This depends on how many other processes requested a port in between the start and restart > of the member. > JGroups relies on the fact that the assignment of ports by the OS is always (not necessarily monotonically) > *increasing* across a single machine. If this is not the case, then the following problems can occur: > 1. Restart: > When a member P crashes and then is restarted, if FD is used and P is restarted *before* it is excluded, > then we have a new member *under the same old address* ! Since it lost all of its state (e.g. retransmission table), > retransmission requests sent to the new P will fail. > 2. Shunning: > Regarding shunning: a member keeps its last N (default is 100) ports used, and makes sure it doesn't reuse one of > those already-used ports when it is shunned. However, this is process-wide and *not* machine-wide, e.g. when we have > processes P1 on A:5000 and P2 on A:5002 (on machine A), and both of them are shunned at the same time, > when they rejoin, P1 does not use port 5000, but might use port 5002, and P2 doesn't use 5002, but might use 5000, so > they could assume each other's identity ! > Both problems cannot be solved by remembering the last 100 ports: in case #1, this list is lost because we start a > new process and in case #2, the list is process-wide, but not machine-wide. > Again, these problems occur *only* when the OS reuses previously assigned ports. > SOLUTION: > A: Use temporary storage (per host) to store the last N addresses assigned on a given host. This makes sure we > don't reuse previous addresses > B: Use logical addresses, such as java.rmi.VMID or java.rmi.server.UID, which are unique over time for a given host. > Then, it doesn't matter what ports we use because the ports are not used to determine a member's identity. > The JIRA task for logical addresses is http://jira.jboss.com/jira/browse/JGRP-129. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JGRP-130) Problems with reincarnation

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-130?page=all ] Bela Ban reopened JGRP-130: --------------------------- > Problems with reincarnation > --------------------------- > > Key: JGRP-130 > URL: http://jira.jboss.com/jira/browse/JGRP-130 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 2.2.9 > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.6, 2.5.2 > > Attachments: tcp.xml > > > Problems with reincarnation > =========================== > Author: Bela Ban > Version: $Id$ > The identity of a JGroups member is always the IP address and a port. The port is usually chosen by the OS, unless > bind_port is set (not set by default). > Let's say a member's address is hostA:5000. When that member dies and is restarted, the OS will likely assign a > higher port, say 5002. This depends on how many other processes requested a port in between the start and restart > of the member. > JGroups relies on the fact that the assignment of ports by the OS is always (not necessarily monotonically) > *increasing* across a single machine. If this is not the case, then the following problems can occur: > 1. Restart: > When a member P crashes and then is restarted, if FD is used and P is restarted *before* it is excluded, > then we have a new member *under the same old address* ! Since it lost all of its state (e.g. retransmission table), > retransmission requests sent to the new P will fail. > 2. Shunning: > Regarding shunning: a member keeps its last N (default is 100) ports used, and makes sure it doesn't reuse one of > those already-used ports when it is shunned. However, this is process-wide and *not* machine-wide, e.g. when we have > processes P1 on A:5000 and P2 on A:5002 (on machine A), and both of them are shunned at the same time, > when they rejoin, P1 does not use port 5000, but might use port 5002, and P2 doesn't use 5002, but might use 5000, so > they could assume each other's identity ! > Both problems cannot be solved by remembering the last 100 ports: in case #1, this list is lost because we start a > new process and in case #2, the list is process-wide, but not machine-wide. > Again, these problems occur *only* when the OS reuses previously assigned ports. > SOLUTION: > A: Use temporary storage (per host) to store the last N addresses assigned on a given host. This makes sure we > don't reuse previous addresses > B: Use logical addresses, such as java.rmi.VMID or java.rmi.server.UID, which are unique over time for a given host. > Then, it doesn't matter what ports we use because the ports are not used to determine a member's identity. > The JIRA task for logical addresses is http://jira.jboss.com/jira/browse/JGRP-129. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4696) Arrange community documents for 4.2.2.GA

by Dimitris Andreadis (JIRA)

Arrange community documents for 4.2.2.GA ---------------------------------------- Key: JBAS-4696 URL: http://jira.jboss.com/jira/browse/JBAS-4696 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Priority: Critical Fix For: JBossAS-4.2.2.GA We *must* produce community documents for AS. At the moment, the only 4.2.x documentation that exists is the EAP one. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

3
17
0 / 0

[JBoss JIRA] Created: (JBAS-4754) Do a full CTS1.4 run to check for regressions.

by Dimitris Andreadis (JIRA)

Do a full CTS1.4 run to check for regressions. ---------------------------------------------- Key: JBAS-4754 URL: http://jira.jboss.com/jira/browse/JBAS-4754 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Other Reporter: Dimitris Andreadis Fix For: JBossAS-4.2.2.GA Before releasing, we should perform a final CTS run. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

2
8
0 / 0

[JBoss JIRA] Commented: (JBMESSAGING-375) Grouping of messages with JMSXGroupId

by Tim Fox (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=comments#action_12... ] Tim Fox commented on JBMESSAGING-375: ------------------------------------- One thought here. Would it be possible to have this functionality working across a cluster too? I.e. all messages sent using a particular value of JMSXGroupid go to the same consumer on the cluster? > Grouping of messages with JMSXGroupId > ------------------------------------- > > Key: JBMESSAGING-375 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-375) Grouping of messages with JMSXGroupId

by Jeff Mesnil (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-375?page=all ] Jeff Mesnil updated JBMESSAGING-375: ------------------------------------ Attachment: patch-JBMESSAGING-375.txt simpler patch: group ID binding is handled directly in RoundRobinDistributor > Grouping of messages with JMSXGroupId > ------------------------------------- > > Key: JBMESSAGING-375 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-375 > Project: JBoss Messaging > Issue Type: Feature Request > Reporter: Tim Fox > Assigned To: Tim Fox > Fix For: 2.0.0 Beta 1 > > Attachments: jbmessaging-375.patch, patch-JBMESSAGING-375.txt, patch-JBMESSAGING-375.txt > > Original Estimate: 1 week > Remaining Estimate: 1 week > > We should add an ability to group messages by JMSXGroupID, so any messages with the same group id always go to the same consumer on a queue. > This would be useful when having competing consumers on a queue and you want each consumer to handle all messages with a particular value of JMSXGroupID -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4869) TECHREVIEW: Installation Guide - Chapter:'Getting Started'

by Vinu S Renish (JIRA)

TECHREVIEW: Installation Guide - Chapter:'Getting Started' ----------------------------------------------------------- Key: JBAS-4869 URL: http://jira.jboss.com/jira/browse/JBAS-4869 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Vinu S Renish -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4868) TECHREVIEW: Installation Guide - Chapter:'Test Your Installation'

by Vinu S Renish (JIRA)

TECHREVIEW: Installation Guide - Chapter:'Test Your Installation' ------------------------------------------------------------------ Key: JBAS-4868 URL: http://jira.jboss.com/jira/browse/JBAS-4868 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Vinu S Renish -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4867) TECHREVIEW: Installation Guide - Graphical Installation

by Vinu S Renish (JIRA)

TECHREVIEW: Installation Guide - Graphical Installation ------------------------------------------------------- Key: JBAS-4867 URL: http://jira.jboss.com/jira/browse/JBAS-4867 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Vinu S Renish -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4866) TECHREVIEW: Installation Guide - Zip Installation

by Vinu S Renish (JIRA)

TECHREVIEW: Installation Guide - Zip Installation ------------------------------------------------- Key: JBAS-4866 URL: http://jira.jboss.com/jira/browse/JBAS-4866 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Vinu S Renish -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 9 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007