Solution : https://service.sap.com/sap/support/notes/1604091 (SAP Service marketplace login required)
Summary :
Messages delivered through File/FTP or JDBC receiver channels are observed to be stuck in DLNG even after channel restarts. This blocking is attributed to the threads responsible for message delivery being in a waiting state due to resource locking in object pools, as revealed by thread dumps. The issue entails threads endlessly waiting for resources due to maximum concurrency being restricted to one thread at a time per channel, as explained in Note 1473299. If poolWaitingTime is misconfigured, threads may wait beyond the specified interval. The solution involves applying a target patch to enhance thread synchronization and resource allocation policies, thus resolving blockages and ensuring efficient message processing.
Key words :
xi xi2file[<channel>/<service>/<party>]_#, xi xi2jdbc[<channel>/<service>/<party>]_#, tid=0x96ecdb0 nid=0x2178 prio=5, tid=0x90067f0 nid=0x2b40 prio=5, consumer threads remain occupied, note 1473299 - setting maximum concurrency, consumer threads serving, moment revels threads, jdbc receiver channel, configured consumer threads
Related Notes :
| 1631887 | ESR,SR,UDDI,MESSAGING related changes in 7.11 SP08 |
| 1631886 | ESR, MESSAGING, SR, UDDI related changes in 7.10 SP13 |
| 1473299 | Setting Maximum Concurrency and poolWaitingTime in File/Jdbc |