Multiple session are open thought Users log out.

[Former Member]

Hello Gurus,

I do see at CMC that many sessions are being open for many days even though users are logged out.

We are using SAP 4.0 (14.0.4)  SP4. It's causing license issues and users are not able to log in.

We have restarted our VM's and clear the IE browsers as well but issue still remains.

Can you please help me on this.

Best Regards,

Sai

[LepreuxLoic]

Hi Sai,

Could you give more information about BOE products you use and for which datasource type (UNV, UNX ?).

I know SP04 still had different issues where multiple sessions were created when working on UNX Universes (see https://support.wdf.sap.corp/sap/support/notes/1764372), and it could lead to "lost sessions". There are other similar problems fixed in more recent versions of BOE, so you may think about upgrading your platform at some point to benefit from all these corrections.

Regards,

Loic

[Former Member]

Hi Loic,

You're correct, We are unisng UNX, i have gone some KBA notes and  UNX universes causes the issues. but this SP04 is very bad have lot of bugs and Data Federation issue while migrating the Universe at first time and partial success of the Promotion Job . Can't change the Webi Report Author name etc.... a lot. We need to bounce our server every alternative day for this multiple sessions open issue.

is there any process to kill/clear the old session?

Best Regards,

Sai

[LepreuxLoic]

Hi Sai,

I don't think there's a simple way to clean old sessions in BI4.0 appart from restarting CMS.

In Central Management Console of BI4.1 you have more information about sessions, and you can kill them one by one ... unfortunately you won't find this in your 4.0 SP04 version.

Best regards,

Loic

[Former Member]

Did you already check the java program that kills sessions?

it will work on BI 4.0 as well, it is discussed in following thread:

[former_member204899]

Hi Former Member

How much time you have set for your default time out?

Br

Prabhith

[sateesh_kumar1]

Hi Sai,

This is because user's may not properly logged of from the system (closed the session).

Try restarting services.