on 08-04-2013 9:50 AM
Dear all,
we read a lot about timeouts in WD4A, but our tests on our SAP system (ERP/EHP6/NW7.31) system show other results - in our production
system we have a lot of timeouts and it is not possible to really clarify what's going on - often the sessions have a timeout after 30 mins, sometimes
the last hours. My last experience was : Rebootet the SAP Server, and i could reconnect in my WD4A app without logon (i was simply in the transaction? Cookie?)
Regarding WD4A (relevant parameters)
We set the following RZ10 parameters and rebootet.
rdisp/plugin_auto_logout : 30 Seconds
WD4A seem to be statefull applications:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/7c/3545415ea6f523e10000000a155106/frameset.htm
so we set the parameter: : c to 2 (ICM should cancel statefull and stateless sessions)
we tried to set parametes with rz11 and restartet (hard) the ICM
Notes from SAP:
Hinweis 1578632 - WebDynpro-Benut.-Session (HTTP/SMTP/..) nach Zeitüb. geschl.
Hinweis 824554 - ICM und SAP Web Dispatcher Timeout Parameter
Hinweis 900804 - Sporadische Fehler bei HTTPS im Internet Explorer
Hinweis 834077 - rdisp/plugin_auto_logout übersteuert ICF timeout
The only parameters which react o.k, is when you set the SICF Timeout - then the session is canceled.
Also an relevant topic is (enabeld), there is a default timeout for security session (30min).
Can anybody describe the exact logic and relevant parameters for timeouts with WD4A? Because in our last tests the sessions last >6 hours (with auto_logout 30 seconds,)
Thanks
Christian
Hello,
try to follow http://scn.sap.com/thread/1185353
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
25 | |
12 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.