BO Session timeout issue

[former_member272418]

Hi guys

I have installed a new BO 4.2 SP05 Patch 02 system.

The below screen shows the architecture of this system:

I set the "session timeout" parameter, on both Tomcats, to 60 minutes.

Then I updated the system to SP08 Patch 02.

After that update, I noticed that the "session timeout" parameter was put back to 20 on both Tomcats. I set it to 60 again but, now I get a strange error.

The test I did is: I log on to the CMC from two different browser sessions, the first passing thru the network load balancer (it's an F5), the second by connecting directly to one of the two Tomcats, without going through the balancer.

If I leave the sessions in idle, without touching anything, after about 13 minutes, in the browser window directly connected to Tomcat, everything is ok and I can navigate the CMC without any problem; in the browser window passing thru the balancer, instead, I get, alternatively, depending on the CMC icon I click, the following three errors:

What do you think about ?

I can't be sure if this problem existed even before the update to SP08, but I only realized it afterwards.

Can I assume that the problem is caused by the network balancer or could it be due to some setting on the Tomcats?

Please help me ! Thank you all very much.

[bernhard_keimel]

I also face issues when using the CMC in Loadbalanced environment. I think that this is an issue coming from the tomcat cluster configuration for session replication. i also see that in the tomcats stderr logs there are millions of entries coming from the SAP internal JARfile implementing the session replication. There is a SAP incident for this running since a year now, by now they managed to fix that in development but it is not delivered yet in a patch release. so i hope that this solves the issues on my side 😉