SM04 Session does not end..Any Idea?

[Former Member]

Hi all,

I noted that SAP R/3 session does not automatically ended after a user logs off from the ESS Frontend. This will result in a increase in session in SM04 eventhough the users had logout from the portal.

I have adjusted some timeout parameter in transaction RZ10 in R/3 including rdisp/plugin_auto_logout and restarted the services. To test, i accessed the ESS Portal and access some IAC IVIEW. Thereafter, i logged off the portal and observed the session created in R/3 (SM04) and noted that the session including the RFC connections are not released at all.

Anyone face this issue before? How can i control so that after the user logoff from the portal, the session in SM04 is end.

Thanks in advance

[SRudra · Accepted solution]

Hi,

Use a programatic approach. there is a method as disconnectIfAlive()... use that to disconnect your RFC connection.... Let us know the code, I could probably help u, where / how u should use it.

Cheers!!!

Sukanta Rudra

[Former Member · Accepted solution]

Hi Sukanta Rudra,

Thanks for your reply, how about other session than the RFC connection. For example I click on my assets in the portal and then I logout from the portal. The transaction code ASEM still hanging in SM04 even though I already logout.

Thanks

Regards

Brian

[SRudra · Accepted solution]

Brian,

The moment you call a logout operation, you should disconnect all connections that are alive and invalidate the node also... I dod not remember excatly, but there are some iView parameters to set the timeout and session logout property... check out them also. Let us know the outcome.

Cheers

Sukanta Rudra

[Former Member · Accepted solution]

Hi Sukanta,

I found some note on the session which i attached below. However in my EP server have dozens of web.xml. Which one should i configure? Would you able to help me on this?

Specifying HTTP Session Timeout

Use

You can specify a timeout period for HTTP sessions created in your Web application. If the session is inactive for this timeout period, it is invalidated by the Web container.

If you do not specify such a timeout explicitly, a default one of 30 minutes is assumed.

You can configure the HTTP session timeout using the web.xml descriptor.

Procedure

On the web.xml screen, proceed as follows:

...

1. Open the General screen.

2. To specify the timeout period, enter a value in the Session configuration – Session timeout field.

The value is specified in minutes. If you enter a negative value in this field, HTTP sessions are never terminated because of a timeout. Instead, only an explicit logout by the user will terminate the corresponding session.

[sreekanthreddy_bommu · Accepted solution]

Hi Sukanta

Can you please let us know where exactly we should use the method disconnectIfAlive()?