2982487 - "A request for server & was sent to server" message when accessing with SAP Web Dispatcher

Symptom

When executing a url, "500 Internal Server Error" is shown in the browser when the session has been inactive for a period longer than the SAP Web Dispatcher HTTP session timeout "wdisp/HTTP/context_timeout" (Default value 3600 seconds)

This can happen, for example, when using an application in the morning without closing the browser the previous day.

The Web Dynpro application shows "A request for server & was sent to server" error message

Executing the same application without SAP Web dispatcher works fine.

Also, after closing and re-started the browser. the error does not occur, as long as wdisp/HTTP/context_timeout is not exceeded.

In the SAP Web dispatcher trace file (dev_webdisp) level 2, the following entries appear:

[Thr <nr>] HTR: found stack ABAP for URL <application url> [Thr <nr>] HTR: routing destination type = ICF/ABAP . [Thr <nr>] HTR: found esid <external session id>- .. [Thr <nr>] IcrITabPurgeEntry(1): entry removed after timeout (idle time=<nr>, context timeout=3600) ... [Thr <nr>] HTR: No server name found in session table; group !DIAG*, <external session id> [Thr <nr>] HTR: ESID backup cookie detected! Applying backup for <external session id>. [Thr <nr>] IcrSessionTabApplyBackup: Applying ESID backup <external session backup id>" .. [Thr <nr>] IcrSessionTabApplyBackup: ESID backup <external session backup id> will be ignored, because context timeout reached!

Environment

SAP Web Dispatcher

Product

SAP Web Dispatcher all versions

Keywords

Internal server error, timeout , KBA , BC-CST-WDP , Web Dispatcher , BC-WD-ABA , Web Dynpro ABAP , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.