2 of 2 people found this helpful
Does anyone know of an RSSO expert from BMC that we can include here? Ideally he also knows a bit about the midtier and a tomcat cluster.
BMC support regularly fails on such a topic between the product worlds (RSSO / Midtier). I think we can overcome this product gap together.
Who is the first
3 of 3 people found this helpful
After a very long and intensive analysis by Uwe Ryczek (our AR/ITSM/RSSO and Java Guru) it is clear that the description of the error behavior is correct. The RSSO agent is to blame for the fact that the Tomcat cluster does not work as desired and the sessions cannot be taken over cleanly by the partner system!
The RSSO Agent/Listener reports all known users in the Tomcat, e.g. when shutting down the MidTier at the RSSO server from EVEN THOUGH it is a Tomcat cluster and the RSSO server destroys the session. In other cases this also applies
So it doesn't matter if the Tomcat was configured as a cluster, the cluster doesn't work as soon as RSSO comes into play as a central component. The users receive a session timeout message from the partner system as a result of these logouts from one Tomcat cluster partner.
I have no idea how I can make this clear to the BMC support without much effort. Maybe there will be a RSSO expert from BMC who will take a quick look here and we can discuss the problem on another technical level. I think all customers would benefit from a timely, general solution. Matt Laurenceau?
I am ready to talk
I am having the same issue with RSSO not working in conjunction with the clustered Mid-Tier/Tomcat servers with session replication enabled.
It appears as the session gets deleted as soon as the corresponding Mid-Tier goes offline and the user is not seamlessly transitioned to the next available mid tier.
Do we have a solution to this problem yet?
1 of 1 people found this helpful
Disable the RSSO filter in the web.xml and the problem is gone. Only comment out the filter, not the rest of the RSSO integration.
Too bad, the bug is still present in the latest RSSO version.
Thanks Stefan. I have the following filter script in the mid-tier web.xml:
If I disable it, the authentication with RSSO fails. Just want to make sure this is the script you were referring to?
Oops, my bad. I meant the listener.
It happens when you answer in your spare time and don't see a system
Thanks Stefan, Let me try it out.
6 of 6 people found this helpful
That’s right Stefan Hall. We remove the whole listener element, because this call's a "session cleanup" routine.
In a Tomcat Cluster environment the replicated sessions are removed (on all nodes!) during shutdown of one cluster node by the RSSOListener.
We are running this configuration for month and do no see any problem by now.
Matt Laurenceau, can you involve an RSSO expert?
BMC Support couldn't handle that and we had to help ourselves. But it is clearly a bug in RSSO since very many versions.
It has fatal consequences and should be fixed.