Solution : https://service.sap.com/sap/support/notes/920979 (SAP Service marketplace login required)
Summary :
In the identified SAP Note, issues related to insufficient memory allocation for the standalone enqueue server in both Java and ABAP environments were encountered, leading to error messages during client request processing. The memory for managing client requests is set at startup and is immutable at runtime. To resolve performance issues, adjusting the profile parameters ‘enqueue/server/max_requests’ and ‘enqueue/server/max_query_requests’ is recommended. In environments requiring high availability and involving a replication server, additional memory adjustments are necessary based on the size of the lock table and system type (Unicode vs. Non-Unicode). Detailed instructions are provided to recalibrate the memory and resource allocations to avoid overload and ensure smooth application operations.
Key words :
enque/server/max_requests sowie enque/server/max_query_requests, enque/server/max_query_requests = 1000 enque/table_size = 500000 scs, enque/server/max_query_requests enque/server/query_block_count, /saphelp_nw70/helpdata/en/39/da8d840167402cb39c5920b340bbb6/frameset, enque/server/max_requests profile parameter, standalone enqueue server requires memory, profile parameters enqueue/server/max_requests, increase enque/server/max_requests, require additional memory resources, enque/server/max_query_requests = 3000
Related Notes :
| 1047180 | Troubleshooting for the standalong enqueue server |
| 834589 | Locking problems in J2EE/Java servers |