Solution : https://service.sap.com/sap/support/notes/1493502 (SAP Service marketplace login required)
Summary :
SAP Note explains the enhancement of the "queueParallelism.maxReceivers" setting, which limits parallel processing threads per receiver, to include Integrated Configurations. Initially, the feature did not account for these configurations leading to potential blocking at the receiver end, similar to classical scenarios. The update allows the property "messaging.system.queueParallelism.queueTypes" to include queues like "icoasync" and "icosync", applicable to Integrated Configurations, enabling finer control over thread usage per receiver, enhancing system efficiency and preventing processing delays due to backend blocking.
Key words :
adding comma-separated values, sap xi af messaging, hanging backend database, max receiver restriction, soap adapter workers, max receiver feature, blocking receiver backend, integrated configuration reason, sender queue worker, asynchronous classical messages
Related Notes :
| 1521931 | ESR,SR,UDDI,MESSAGING related changes in 7.11 SP06 |
| 1511517 | SAP EHP1 FOR SAP NETWEAVER PI 7.1 SP06 |
| 1136790 | Blocking receiver channel may affect the whole adapter type |