HTTP Cluster with Catalina

[banigreyling]

Hi

Can someone give some indication of how to set up distributed catalina on JBoss_3.0.1-Tomcat_4.0.4.

I uncommented "SnapshotMode" and "SnapshotInterval" in "tomcat4-service.xml and I have added "" in my web.xml. It then give me the error:
INFO [EmbeddedCatalinaServiceSX] ClusteredHTTPSessionService not found
ERROR [EmbeddedCatalinaServiceSX] Failed to setup clustering, clustering disabled

Thnx
Bani

[dgantenbein]

Hi -

Make sure that you add /docs/examples/clustering/jbossha-httpsession.sar to your deploy directory.

Dorothy

[banigreyling]

Thanks, jbossha-httpsession.sar got rid of my initial error.

I got the ClusteredHTTPSessionService up and running. But now my session does not seem to get replicated to my second instance on another machine. Any idea what I must do to get it replicating.

Thanks

[jorju]

Hi all,

does jbossha-httpsession.sar work ok ? (i believe not)

I've got the ClusteredHTTPSessionService up and running.

But session does not get replicated !!!

(I'm running 2 Jboss-3.0.1/tomcat-4.0.4 bundle on LinuxRH)

and session replication works well with both of these
tomcats (the ones bundled with jboss)!!! (using javagroups.jar v2.1, tomcat-javagroups.jar and UDP protocol stack for InMemoryReplicationManager)

i've tried all possible combinations with both
jboss (and their tomcat4-service.xml) but seems like JBoss handles by itself session replication
(through jbossha-httpsession.sar) witn no success (and
worst, with no logs, traces that explain such a session replication problem)

additionally,
putting distributable property in web.xml will cause
to loose session afinity ! (loosing sticky sessions)
(and session still won't replicate !!!)

Is anyone in a similar situation ?
Does someone know what is happening with jbossha-httpsession.sar ?

Thanks in advance

[jorju]

Hi all,

does jbossha-httpsession.sar work ok ? (i believe not)

I've got the ClusteredHTTPSessionService up and running.

But session does not get replicated !!!

(I'm running 2 Jboss-3.0.1/tomcat-4.0.4 bundle on LinuxRH)

and session replication works well with both of these
tomcats (the ones bundled with jboss)!!! (using javagroups.jar v2.1, tomcat-javagroups.jar and UDP protocol stack for InMemoryReplicationManager)

i've tried all possible combinations with both
jboss (and their tomcat4-service.xml) but seems like JBoss handles by itself session replication
(through jbossha-httpsession.sar) witn no success (and
worst, with no logs, traces that explain such a session replication problem)

additionally,
putting distributable property in web.xml will cause
to loose session afinity ! (loosing sticky sessions)
(and session still won't replicate !!!)

Is anyone in a similar situation ?
Does someone know what is happening with jbossha-httpsession.sar ?

Thanks in advance

[derry]

I need your server.log for a deeper analisys....

CU
Thomas

[derry]

I need your server.log for a deeper analysis...

CU
Thomas

[derry]

Hi,

I need your server.log for a deeper analysis...

CU
Thomas

[derry]

Hi!

I need your server.log to analyze your problem...

CU
Thomas

[derry]

Hi!

I need your server.log to analyze your problem...

CU
Thomas

[jorju]

Hi,

Thanks very much for tour interest
(and excuse me for my delay)

I still have to try it with the new sources
http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t=forums/ again

[derry]

Hello!

You should use a "fresh" catalina-build. It seems that you have NO -tag in your web.xml. There is no webapp that triggers the cluster code...

CU
Thomas

[jorju]

Seems the new sources solved my problem

but ...
session failback isn't yet achieved !

that means,
- load balancing and session afinity seem now to work
the right way
(i.e. SessionIds Sad06NhOOs91G9qEk+gflw**.server1)
- launch the 2 clustered-servers and fill the session of one of them: we'll call this server "server1"
(although i have debug="99" in most xml i cannot
see any session replication logs :-(
- stop server1
- try to continue filling your session (using the same
sessionId)
- yujuuuuu !, session is being replicated
(although i still haven't got any logs that confirms it)
- now launch again the dead server ("server1")
when it finishes launching it should replicate the
current session in server2 but...
- try to continue filling your session:
wops !, a new session ? where did my shopping cart go ?

is it session failback already implemented ?

Thanks

[jorju]

One more thought ...

i was so happy to see that, finally, the session get
replicated that i deleted jvmRoute="worker_as_in_workers.properties_name"
from tomcat4-service.xml to force the lost of
session affinity

i believed that (as session was now replicated) session
affinity was useless (without taking into accout performance boost) from a theoric point of view.

but, i was very disappointed to see that losing session
affinity also causes to loose session replication :-(

so, my final situation is:
session affinity + HTTP in-memory session replication + without session failback ! :-(

is there such a way to improve this situation ?

[derry]

Hello!

OK. This may be a bug. At work we use a hardware loadbalancer and the sessions stays at the LAST machine that answered the request. So if you are on server1 and get a failover to server2 you stay there even when server1 comes back again. I will investigate...

CU
Thomas