Now, there is a continuation of my story. Here is what I want to achieve:
I want to run a cluster (say, hostnames node1 and node2) with apache2 + mod_jk
loadballancer (hostname apache) with failover and loadballancing capabilities
and SSO across multiple applications. There are two
I checked what you wanted me to and confirm that the TreeCache is up and
running.
Here is what I get on the stdout (Sorry for the huge log)
|
===
| .
| JBoss Bootstrap Environment
| .
| JBOSS_HOME:
I kept investigating the problem and found the difference betweeen the machine
where Clustered SSO works for me and the one where it doesn't. Moreover, I
found the root of described the problem!
Apparently some time ago I wanted to be able to reach jboss JVM via sun's
jconsole, therefore I
Again, here are the datailed steps I took to get this odd behaviour surface.
1. Take the standard all configuration. It has all in store (session
replication via TreeCache defined in tc5-cluster-service.xml)
2. Add the dependency on the jboss.cache:service=TomcatClusteringCache to the
I'am constantly getting this on both server startup as well as on each SSO
replication event.
16:45:53,212 INFO [TreeCacheSSOClusterManager] Cannot find TreeCache using
jboss.cache:service=TomcatClusteringCache --
| treeCacheName must be set to point to a running TreeCache before
