SAP Knowledge Base Article - Preview

2532398 - Web Dispatcher - Load balancing fail after some time.

Symptom

  • The Web Dispatcher is performing the load balancing properly, but after some time you see a huge usage in only one instance of backend. 
  • The following entries are visible on Web Dispatcher trace level 2 (dev_webdisp):

[Thr 1] HTR: Adding session id <Generic ID>, group !DIAG* to session table, server APPSERVER1_SID_00
[Thr 1] IcrITabInsertEntry(1): FtInsert failed
[Thr 1] HTR: Failed to insert session, cleanup old entries.
[Thr 1] IcrITabInsertEntry(1): FtInsert failed
[Thr 1] HTR: Failed to insert session, use default server.
[Thr 1] IcrITabGetEntry(1): key: 0:1999398162, inst_name: APPSERVER3_SID_00
[Thr 1] HTR: HtrIUpdateSessionTable: rc=-3, opt=2, session id ICR_DEFAULT_SESSION_ID, group !DIAG*


Read more...

Environment

  • SAP Netweaver release independent
  • Web Dispatcher

Product

SAP NetWeaver all versions

Keywords

ESID, wdisp/HTTP/context_timeout, wdisp/HTTP/max_session_tab_entries, Session Dispatching, 503, overload, freeze, users, disconnect, SAP Webdispatcher Admin tool, admintool, webadmin , KBA , BC-CST-WDP , Web Dispatcher , BC-CST-IC , Internet Communication Manager , 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.