Hi Ragini,
I am sorry, but we were not able to overcome this. So as not to waste a lot
of time on it (time = money), we decided to just kill the JBoss process as
opposed to allowing a graceful shutdown. This had the desired effect. There
is, of course, some risk in this approach, but we
If all I want is Session replication, I need the tc5-cluster.sar application.
The guide you pointed to is an all-or-nothing removal of clustering.
It is my understanding that underneath the hood, the tc5 clustering uses JBoss
Cache. I'm not sure how everything's plumbed together, so I'm just
Anyone?
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4006983#4006983
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4006983
___
jboss-user mailing list
jboss-user@lists.jboss.org
Thank you for your response. It got me thinking, so I did a little digging. I
found fail_on_status worker directive for the status worker. It should allow
me to trap the 404 and 500 errors as failures, and automatically switch to
another node. I'll report back results.
Thanks again,
Alan
I was under the impression that
C:\jboss-4.0.5.GA\server\hmc\deploy\tc5-cluster.sar\META-INF\jboss-service.xml
was the new, cool place to configure http session replication. I set it up to
use tcp, works great and everything, yet I get
20:44:36,484 ERROR [UDP]
I have a two-node cluster (Apache v2.2, JBoss 4.0.5.GA) with HTTP session
replication set up per instructions in the JBoss documentation. Everything
works great. Except... During the time that jboss is shutting down on one of
the servers, Apache will still direct requests to it. Because my
