Solution : https://service.sap.com/sap/support/notes/919196 (SAP Service marketplace login required)
Summary :
This SAP Note addresses issues related to improper session release or inability to execute Java or ABAP BEx Web applications on ABAP SAP Web Application Servers. Sessions are incorrectly managed due to flaws in the BEx Web application session handling mechanisms. Specifically, two main error scenarios include a persistent browser window hinting at backend sessions not ending rightly, and application inaccessibility when reaching the maximum connections limit. The remedy involves ensuring proper session termination strategies, such as explicit log-offs, navigating away from the app, or browser close. Additionally, problems may arise if "dialog box blockers" are enabled which prevent session closure notifications to the server, especially noted with browsers like Internet Explorer in Windows XP SP2 where these blockers are active by default.
Key words :
longer execute java bex web applications, abap sap web application server, java sap web application server, abap bex web applications, abap bex web application, web browser runs crashes, windows xp support package 2, dialog box blocker product, bex web applications, bex web application
Related Notes :
| 1159538 | Issues in Internet Explorer after you uninstall front end |
| 1029680 | BEx Web applications Java: Limiations for Firefox |
| 917950 | SAP NetWeaver 2004s: Setting Up BEx Web |
| 596698 | Session Release Agent - Typical Problems & Troubleshooting |