1 of 1 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
2 of 2 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