-
1. Re: clustering with more than 2 nodes.
alanlewis Jan 7, 2002 11:07 PM (in response to edwu00)Hi Ed,
Glad to hear you were able to get clustering working with the alpha. I can't say I've had a chance to try clustering to work with more than two nodes, but in looking at your log file I see something familiar. When I was first trying out clustering I was having JBoss freeze at startup. I then found out that the problem was the machine I was using had a dynamic IP address. Could it be the case that the third machine you are trying to add maybe has a dynamic IP address?
-Alan -
2. 375453
slaboure Jan 8, 2002 4:54 AM (in response to edwu00)If this DHCP thing makes the trick, then you are entirely right Alan: this has to go in the doco!
-
3. Re: clustering with more than 2 nodes.
alanlewis Jan 8, 2002 11:16 PM (in response to edwu00)Well, please let me know if it does.
So Sacha or Bill, how about putting this info in the docs? -
4. Re: clustering with more than 2 nodes.
edwu00 Jan 9, 2002 5:00 PM (in response to edwu00)Now 3 nodes work for me.
I am using static IP machine.
So it is obvious the problem is DHCP.
Thanks for all the help.
Ed Wu -
5. Re: clustering with more than 2 nodes.
slaboure Jan 11, 2002 8:23 AM (in response to edwu00)So you win Alan ;)
I will update this in the next doco.
Thank you!
Cheers,
Sacha -
6. Re: clustering with more than 2 nodes.
bill.burke Feb 25, 2002 12:42 PM (in response to edwu00)Sorry guys, I don't follow forums very much. Email me directly with any problems and I will be happy to help.
Anyways. I run with DHCP all the time. Maybe your DHCP is giving your machine a non-routable ip address for MCast?
Have you tried out the 3.0 beta? I've used 3 machines for a cluster just fine.
Please let us know directly about any problems and I'd be curious to hear about your 18 node configuration! -
7. Re: clustering with more than 2 nodes.
slaboure Feb 26, 2002 5:31 AM (in response to edwu00)Bill,
I don't think the 2 nodes problem was only related to DHCP. JG seems to have a problem with DHCP (at least on Windows) but we also had, a few weeks ago, a bug which prevented already running client proxies to receive the new cluster view automatically. Newly started clients were ok but refreshing of already running clients was not.
cheers,
Sacha