Timeout error with BO Explorer 4.2 in BI launchpad with BO4.2 SP03

[Former Member]

Hello,

Our users are receiving a timeout error message in Infospace while in the BOE Launchpad. Our BOE timeout setting in Tomcat is 20 mins. We disable Explorer timeout = -1. Through testing and monitoring CMC session, we see that two sessions are created: BOE and Explorer.

One result we see during testing between 10-20 mins the BOE session is killed and Explorer session remain; users get the invalid logon token error message.

Second result we see during testing between 10-20 mins the Explorer session is killed and BOE session remain, however we still are able to perform exploration. After 40-60 mins we get the invalid logon token error message and we see that the BOE session is killed.

We get different results every time we time and cannot pinpoint the problem. Can someone shed light on why all sessions aren't killed after the 20 min timeout set in BOE (web.xml)?

Thank you ahead!

[former_member312343 · Accepted solution]

Thank you all for your help!!

We did open the case with SAP unfortunatly the employee working on the case is out till Monday...

Good news is if found the solution and fixed the problem.

The problem was in BO session management. Every time we login in BI Launchpad via SSO BO created AD session called BI Launchpad Session and when we open explorer it created another AD session called Explorer session. So we end up with 2 session doing the same job. After sometime BO session failover knocked out BI Launchpad session... and that is where the problem was.

After some investigation I figured out that as part of exploration servers default services Explorer was forced to SSO in and create a new AD Session every time we open Explorer infospace. To make long story short the fix was to disable SSO for explorer and since we access Explorer via BI Launchpad explorer utilize BI Launchpad session... and we end up with one session "BI Launchpad". I test the system multiple times for more than 90 minutes everything is working as it should.

Happy Friday everyone and Thank you all for your support,

Waleed

[Former Member · Accepted solution]

By disabling Explorer SSO and changing explorer's session timeout to 2mins we ensure that users' sessions are killed in 2mins if they close IE browser,