I am posting the solution that I have put in for the problem posted here. I
changed the cluster config to use instead of FD_SOCK and am no longer
experiencing the timeout issue.
The cluster documentation mentions that when FD_SOCK is used, a member is
declared dead only when socket is closed.
Brian, Thanks a lot !
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3914629#3914629
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3914629
---
This SF.net email is
Thanks for your response.
From what I understand from jboss cluster documentation, I need to separate
the partition and cluster. Pl clarify on what u mean by 3 clusters.
This is how I start jboss :
run -c all -Djboss.partition.name= -Djboss.cluster.name=
View the original post :
Hi all,
Each developer in my team is running a single node cluster instance (jboss
4.0.1 on windows XP) on his/her machine by specifying a unique jboss partition
name and a unique jboss cluster name. We can see messages on the jboss console
that confirm that on each developer's instance that
Thanks for ur response!
There is no firewall between my app and database as I am running on a dev
environment. Also the same application when run on tomcat against the same
database (which we have been doing for a while now) has never encountered this
issue.
What I am noticing now is that
Hi all,
I am running JBOSS 4.0.1 on Windows. I have a client code within Jboss that
connects to the same jboss server URL (this is part of CAS authentication).
All is well when Jboss starts up initially. But if I leave my Jboss server
running overnight and try accessing it after a period of
Hi all,
I am running JBOSS 4.0.1 on Windows. I have a client code within Jboss that
connects to the same jboss server URL (this is part of CAS authentication).
All is well when Jboss starts up initially. But if I leave my Jboss server
running overnight and try accessing it after a period of
