Solution : https://service.sap.com/sap/support/notes/1234847 (SAP Service marketplace login required)
Summary :
When executing a WebDynpro for Java application in the NW04s version, users may encounter com.sap.tc.webdynpro.services.session.LockException. This exception is due to Web Dynpro's single-threaded framework where each user session can be locked by one thread during request processing, leading to serialized concurrent requests. If a request hangs, subsequent requests will time out and show a LockException error page. To diagnose, SAP requires thread dumps taken immediately post-exception via the procedures outlined in Note #710254, along with screenshots of the error and default trace files from the server node. Adjustments like setting "sap.locking.maxWaitInterval" can manage lock waiting times.
Key words :
single-threaded programming model, latest default trace file, intended long running requests, shared client session locks, exclusive client session lock, client session clientsession, acquire exclusive lock, app session locks, waiting/blocking condition, concurrently incoming requests
Related Notes :
| 1113811 | Web Dynpro error page, known error situations, error codes |