We have a Java RFA v. 8.0.1 consumer that maintains an item reference database by keeping open streams 16 symbol lists defined as BDSs in our Edge (our path is Consumer -> ADS -> ADH -> Edge).
For simplicity all 16 streams are opened at the same time even though only one stream provides refresh messages while the rest of the streams reports "Item Request Timeout".
Only when a refresh is completed the next stream starts supplying refresh messages until all 16 are done.
In general that works fine but now and then the symbol lists responds with states like :
F2:Source application did not respond.
Waiting for service XXX. Item recovery in progress...
No connection or service is currently up that supports this request.
It's not clear to us if these states are generated by ADH, ADS or Edge ?
Are these states side-effects of asking Edge to maintain databases of effectively all items available on the ILA ?
Does TR have any recommendations or guides on how to tune Edge to support this kind of usage ?