Hi,
I'm having same problem with my Jobss instances, same version same setup. So my
first question is if you'v managed to cluster the services and how in that case?
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4211427#4211427
Reply to the post :
http://ww
First off I turned org.jgroups to "TRACE", however I'm unsure how to read the
results of this,but then I also started the 2 cluster members and attempted to
probe the jgroup, as discussed at http://wiki.jboss.org/wiki/Probe:
[EMAIL PROTECTED] lib]# /opt/jdk1.6.0_02/bin/java -cp jgroups.jar
org
Have a look at first item on http://wiki.jboss.org/wiki/ClusteringFAQ and
following the link from there to the Troubleshooting section on the JGroups
wiki page.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4161831#4161831
Reply to the post :
http://www.jb
I also tried adding java.naming.provider.url=172.19.2.10:1100:172.19.2.11:1100
to the all/conf/jndi.properties file, which force the a set of nodes. This
causes the first member to be brought up to throw exceptions, saying it can not
contact the second member (which is understandable), but the s
