[Clustering/JBoss] - Re: Configuration for redundant ethernets
by alpheratz-jb
Setting compatibility mode worked...I think.
I now get:
| [root@bob1 bin]# ./probe.sh
|
| -- send probe on /224.0.0.75:7500
|
|
| #1 (332 bytes): 147.209.225.205:37848 (TCEPartition)
| local_addr=147.209.225.205:37848
| group_name=TCEPartition
| version=2.4.1, cvs="$Id: Version.java,v 1.42.2.1 2006/12/04 13:57:06 belaban Exp $"
| view: [147.209.225.205:37848|3] [147.209.225.205:37848, 147.209.225.205:37853, 147.209.225.208:33260, 147.209.225.208:33266]
| group_addr=230.0.0.88:45566
|
|
| #2 (346 bytes): 147.209.225.205:37846 (Tomcat-TCEPartition)
| local_addr=147.209.225.205:37846
| group_name=Tomcat-TCEPartition
| version=2.4.1, cvs="$Id: Version.java,v 1.42.2.1 2006/12/04 13:57:06 belaban Exp $"
| view: [147.209.225.205:37846|3] [147.209.225.205:37846, 147.209.225.205:37851, 147.209.225.208:33258, 147.209.225.208:33264]
| group_addr=230.0.0.88:45577
|
|
| #3 (332 bytes): 147.209.225.205:37853 (TCEPartition)
| local_addr=147.209.225.205:37853
| group_name=TCEPartition
| version=2.4.1, cvs="$Id: Version.java,v 1.42.2.1 2006/12/04 13:57:06 belaban Exp $"
| view: [147.209.225.205:37848|3] [147.209.225.205:37848, 147.209.225.205:37853, 147.209.225.208:33260, 147.209.225.208:33266]
| group_addr=230.0.0.88:45566
|
|
| #4 (346 bytes): 147.209.225.205:37851 (Tomcat-TCEPartition)
| local_addr=147.209.225.205:37851
| group_name=Tomcat-TCEPartition
| version=2.4.1, cvs="$Id: Version.java,v 1.42.2.1 2006/12/04 13:57:06 belaban Exp $"
| view: [147.209.225.205:37846|3] [147.209.225.205:37846, 147.209.225.205:37851, 147.209.225.208:33258, 147.209.225.208:33264]
| group_addr=230.0.0.88:45577
|
|
| #5 (332 bytes): 147.209.225.208:33266 (TCEPartition)
| local_addr=147.209.225.208:33266
| group_name=TCEPartition
| version=2.4.1, cvs="$Id: Version.java,v 1.42.2.1 2006/12/04 13:57:06 belaban Exp $"
| view: [147.209.225.205:37848|3] [147.209.225.205:37848, 147.209.225.205:37853, 147.209.225.208:33260, 147.209.225.208:33266]
| group_addr=230.0.0.88:45566
|
|
| #6 (332 bytes): 147.209.225.208:33260 (TCEPartition)
| local_addr=147.209.225.208:33260
| group_name=TCEPartition
| version=2.4.1, cvs="$Id: Version.java,v 1.42.2.1 2006/12/04 13:57:06 belaban Exp $"
| view: [147.209.225.205:37848|3] [147.209.225.205:37848, 147.209.225.205:37853, 147.209.225.208:33260, 147.209.225.208:33266]
| group_addr=230.0.0.88:45566
|
|
| #7 (346 bytes): 147.209.225.208:33264 (Tomcat-TCEPartition)
| local_addr=147.209.225.208:33264
| group_name=Tomcat-TCEPartition
| version=2.4.1, cvs="$Id: Version.java,v 1.42.2.1 2006/12/04 13:57:06 belaban Exp $"
| view: [147.209.225.205:37846|3] [147.209.225.205:37846, 147.209.225.205:37851, 147.209.225.208:33258, 147.209.225.208:33264]
| group_addr=230.0.0.88:45577
|
|
| #8 (346 bytes): 147.209.225.208:33258 (Tomcat-TCEPartition)
| local_addr=147.209.225.208:33258
| group_name=Tomcat-TCEPartition
| version=2.4.1, cvs="$Id: Version.java,v 1.42.2.1 2006/12/04 13:57:06 belaban Exp $"
| view: [147.209.225.205:37846|3] [147.209.225.205:37846, 147.209.225.205:37851, 147.209.225.208:33258, 147.209.225.208:33264]
| group_addr=230.0.0.88:45577
|
|
|
| [root@bob1 bin]#
|
My partition is 'TCEPartition'/45566. I can now see entries for 'Tomcat-TCEPartition'/45577 as well.
Is this correct? it is certainly different.
Also, consider this:
| [root@bob1 bin]# ./probe.sh -addr 230.0.0.88 -port 45566
|
| -- send probe on /230.0.0.88:45566
|
|
|
| [root@bob1 bin]#
|
in my log, I see:
| 2007-04-11 09:33:00,434 WARN [org.jgroups.protocols.UDP] packet from 147.209.225.205:42856 has different version (20821) from ours (241). This may cause problems
| 2007-04-11 09:33:00,435 ERROR [org.jgroups.protocols.UDP] failed unmarshalling message
| java.io.EOFException
| at java.io.DataInputStream.readBoolean(DataInputStream.java:222)
| at org.jgroups.util.Util.readAddress(Util.java:472)
| at org.jgroups.protocols.TP.bufferToList(TP.java:1021)
| at org.jgroups.protocols.TP.handleIncomingPacket(TP.java:827)
| at org.jgroups.protocols.TP.access$400(TP.java:45)
| at org.jgroups.protocols.TP$IncomingPacketHandler.run(TP.java:1296)
| at java.lang.Thread.run(Thread.java:595)
|
Not what I expected...and not what WAS happening
FYI, my probe.sh is:
| #!/bin/sh
| ### ====================================================================== ###
| ## ##
| ## JGroups Cluster Discovery Script ##
| ## ##
| ### ====================================================================== ###
|
| # Discovers all UDP-based members running on a certain mcast address (use -help for help)
| # Probe [-help] [-addr <addr>] [-port <port>] [-ttl <ttl>] [-timeout <timeout>]
|
| # CLASSPATH=.:../lib/commons-logging.jar:../server/all/lib/jgroups.jar:$CLASSPATH
|
| JAVA_HOME="/opt/jrockit-R27.1.0-jdk1.5.0_08"
| JBOSS_HOME="/opt/jboss-4.0.5.GA"
|
| CLASSPATH=.:$JBOSS_HOME/lib/commons-logging.jar:$JBOSS_HOME/server/ports-02/lib/jgroups.jar:$CLASSPATH
|
| # OS specific support (must be 'true' or 'false').
| cygwin=false;
| case "`uname`" in
| CYGWIN*)
| cygwin=true
| ;;
| esac
|
| if [ $cygwin = "true" ]; then
| CP=`cygpath -wp $CLASSPATH`
| else
| CP=$CLASSPATH
| fi
|
| $JAVA_HOME/bin/java -Djgroups.marshalling.compatible=true -cp $CP org.jgroups.tests.Probe $*
|
The actual cluster seems OK...we are just talking about the behaviour of probe.sh (aren't we?).
Cheers,
Alph
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036175#4036175
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036175
19 years
[JNDI/Naming/Network] - JNDI, HAJNDI and jboss.bind.address
by paulkmoore
Hi - I'm hoping somebody can help.
I have a multi-homed machine and I'm trying to configure sensible bindings for the various services in order that the exposed application interfaces are as limited as possible.
I've investigated the -b (or --host) runtime parameter to set the jboss.bind.address and bind.address (JGroups) bindings. There is some success here, the JNDI and HAJNDI services are listening on the protected interfaces, and the JGroups services UDP traffic is binding over the same interfaces (confirmed via netstat -gn).
However, if I understand correctly, the entire HAJNDI implementation is transparent to the calling EJBs through effectively an internal re-write of the InitialContext() call. However, as such services are typically provided via localhost and such services are no longer bound to this IP address I am receiving the (apparently) classic "javax.naming.CommunicationException: Could not obtain connection to any of these urls: localhost:1100". This error doesn't seem unreasonable given that nothing is listening on the localhost:1100 port.
Am I missing something simple, as I'm sure most enterprise deployments will have experienced such. Additionally, I've seen in various posts mention of 'binding-services' as a way to over-ride key services - however the documentation on this topic is limited to say the least.
Any thoughts or pointers welcomed
Thanks
Paul
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036166#4036166
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4036166
19 years