I have a JBoss cluster, v4.0.3, with two nodes. Load balancing uses mod_jk, but
without sticky-session.
I am having problems when a session is invalidated and then a new set of
attributes set in a new session (i.e. someone logs out, then logs in again as a
different user).
HttpSession sess =
I was reading through the JBoss AS Clustering ED 7 PDF and noticed that on page
74 or the PDF it refers to jbossha-httpsession.sar which I can't seem to find
in my jboss-4.0.2 installation. I do see a httpha-invoker.sar. Are these 2
.sars equivalent? If not how does HTTP session replication,
Hi!
We set up a cluster of 2 JBoss/Tomcat (4.0.1) nodes using both EJB and HTTP
session clustering (replication). Although in most cases the HTTP session
replication works fine (you can access servlets on both nodes with the same
session id :-)) after some time, say 1 minute up to 1 day, the
Hello all Jboss gurus out there,
I am having a development environment with following details,
I have two intel p4 machines with 2 GB RAM, RedHat Linux running on it and
having 3 Jboss-4.0.0 instances.
Machine 1:
Instance 1: running in all mode and having DEVPartition as cluster
partition.
I have a stress test tool that does lots of JSP fetches without retaining any
cookies between requests. The container therefore is creating a new session for
each request (which is the expected behavior) and my JSP code is setting a few
session attributes when it sees it's dealing with a new
Hello!!!
I have 2 box (win2000 and RH 9.0) with jboss3.2.3 and apache2 with mod_jk2 on
other box.
In tomcat jboss-service.xml i added jvmRoute=server1 and jmRoute=server2.
Running on default config with cluster-service.xml and jbossha-httpsession.sar
on RH9.0 i added
route add -net 224.0.0.0
Hi all,
We are setting up a cluster of servers, the specifications are as follows:
OS: Windows 2000 Professional
JDK: jdk1.3.1_04
JBoss version: jboss-3.2.1_tomcat-4.1.24 (on 2 nodes viz server1 and server2.)
Apache: 2.0.45(installed on server1)
We have included distributable/ element in the
Hi!
In case of http session replication, is the session replicated to all nodes in the
cluster or to an identified secondary node only? I do not see the 'clustering
documentation' explicitly state this.
View the original post :
Hi!
In case of http session replication, is the session replicated to all nodes in the
cluster or to an identified secondary node only? I do not see the 'clustering
documentation' explicitly state this.
View the original post :
