You will need to post a lot more information than that! :-)
- your cluster config
- are all your nodes on the same machine?
- have you tried the JGroups tests - http://www.jgroups.org/javagroupsnew/docs/newuser/node13.html
- anything in your error logs
are all your nodes on the same machine?
No. I am running it in different machine
My cluster config file
here i am adding the lines which i changed
4. worker.properties in appache/conf
# Define Node1
# modify the host as your host IP or DNS name.
# Load-balancing behaviour
# Status worker for managing load balancer
These are the changes i have done, there is no error in the log, simply in the application we are verfiying for the user session if the session is not there we are redirecting to login page.
Everthing working fine with sticky session
xml tags are missing
Engine name="jboss.web" defaultHost="localhost" jvmRoute="node1"
attribute name="UseJBossWebLoader" = false
attribute name="UseLocalCache = false
attribute name="UseJK" = true
Session replication is working when we change the worker.properties
worker.loadbalancer.sticky_session=0 to 1
when the first server fails, the user is redirected to the second server and the session of the user is available in the second one can you please explain me how it is working
Hi there. This is the typical characteristic of sticky sessions, where all requests for a given session are directed to a single server until that server fails.
I have a related problem regarding loadbalancing and session sharing.
I have worker.loadbalancer.sticky_session=1 in my worker.properties file on Apache. ( Let me know if I should send the complete worker.properties). Yet, the loadbalancer seems to be trying to send requests to both the servers. The first page goes to the first server and when I try submitting the page, the request goes to the second server.
And it seems like the session information has not been shared between the 2 servers yet. Because the response page has most elements missing. Only static logos and links show up. None of the real application elements are showing up.
I have set the JVMRoute='nodename' in server.xml on both servers.
An interesting thing I noticed was the when I tried to set the UseJK attribute to true in jboss-service.xml, the server would not start up and would give an error in JVMRouteFilter. So have run the server without this. But clustering works. Am using JBoss 4.0.0.
Suprisingly, failover works fine. When a server goes down, the other server picks it up instantly. I can see that the 2 servers have recognised each other and formed a cluster. Tried the jgroups Draw test recommended here too. works fine.
i think in JBoss 4.0.0 we dont need to add the attribute useJK, now we are using jBoss 4.0.2RC1 everything works fine in jboss ... but some time apache showing service not available ... if i refresh the page the page get loaded....
You should set the useJK flag in 4.0.2. There was a problem with the JVMRouteFilter in 4.0.0 (see issue 1037726 on Sourceforge), but that was fixed in 4.0.1.