Client has two EEDs and one EED occurred comms outage issue at 12:00 GMT+8, Apr.26 and restored after replace Juniper Router at 9:55 GMT+8, Apr.27. As there are two EDGE servers in client site, the 2nd EED was working well during the 1st one outage. Client app SHOULD be able to receive updates normally. But as client said, he had to restart client app for service restore. TSG believes this is API app issue that it could not receive updates after get “ERROR: ItemManager Receive a COMPLETION_EVENT” message. Could RDC advise what the problem is and how to solve it? Thanks.

Src_dist.log on shrmds1: <shrmds1.1.src_dist.serviceGenerator.route_rdf1.route.IDN_SELECTFEED: Warning: T hu Apr 26 12:57:16 2018> The datafeed links are bad and discourageRequestsOnOutage is enabled. The server will discourage item requests by raising its load factor to 65535 (th e maximum). <END> <shrmds1.1.src_dist.rrmpConsumer.IDN_SELECTFEED.257.hotStandby: Info: Thu Apr 26 12:57:16 2018> Active server IDN_SELECTFEED is going standby. Ok Items saved: -333 <END> <shrmds1.1.src_dist.serviceGenerator.route_rdf1.route.IDN_SELECTFEED: Warning: T hu Apr 26 12:57:16 2018> SrcStreamService initiating consumer side shutdown.Reason: Server is being force d to go standby Server will be removed from network. <END> <shrmds1.1.src_dist.rrmpConsumer.IDN_SELECTFEED.257.hotStandby: Info: Thu Apr 26 12:57:16 2018> Active server IDN_SELECTFEED is going standby. Ok Items saved: -333 <END> <shrmds1.1.src_dist.rrmpConsumer.FailbackTransportMgr.failbackTransport: Info: T hu Apr 26 12:57:16 2018> Hot-standby auto failback UDP channel enabled. The configurataion is: Multicast address: 238.3.3.3 Multicast service: 9023 Multicast interface: 192.9. 100.2 <END> <shrmds1.1.src_dist.rrmpConsumer.IDN_SELECTFEED.257.hotStandby.HSAutoFailback: I nfo: Thu Apr 26 12:57:16 2018> The converted configuration is: Multicast recv address: 238.3.3.3 Multicast send address: 238.3.3.3 Multicast se rvice: 9023 Multicast interface: 192.9.100.2 <END> <shrmds1.1.src_dist.rrmpConsumer.IDN_SELECTFEED.257: Info: Thu Apr 26 12:57:16 2018> Server IDN_SELECTFEED is going Standby with peer. <END> <shrmds1.1.src_dist.serviceGenerator.route_rdf1.route.IDN_SELECTFEED: Info: Fri Apr 27 10:52:26 2018> The datafeed links are good. The server will no longer discourage item requests. <END> P2ps.log on sh1rmds1: <shrmds1.1.p2ps: Info: Thu Apr 26 12:57:16 2018> Source IDN_SELECTFEED has changed its server id from 45000 to 258 <END> <shrmds1.1.p2ps: Info: Thu Apr 26 12:57:16 2018> Source IDN_SELECTFEED has changed its server id from 258 to 45000 <END> Note: there are 57 mins time gap on shrmds1 Src_dist.log on shrmds2: <shrmds2.1.src_dist.rrmpConsumer.IDN_SELECTFEED.258: Info: Thu Apr 26 12:44:05 2018> Standby Server IDN_SELECTFEED is going Active with no peer. <END> <shrmds2.1.src_dist.rrmpConsumer.IDN_SELECTFEED.258.hotStandby: Debug: Thu Apr 2 6 12:44:05 2018> Standby dirty item counts at the time of failover. openStateDiff: 0 openStateTimeDiff: 291 notOpenActive: 0 recovItems: 0 nonRecovItems: 0 sinkDiff: 0 <END> <shrmds2.1.src_dist.rrmpConsumer.IDN_SELECTFEED.258: Info: Thu Apr 26 12:44:05 2018> Active server IDN_SELECTFEED is going Active with peer. <END> P2ps.log on shrmds2: <shrmds2.1.p2ps: Info: Thu Apr 26 12:44:05 2018> Source IDN_SELECTFEED has changed its server id from 45000 to 258 <END> <shrmds2.1.p2ps: Info: Thu Apr 26 12:44:05 2018> Source IDN_SELECTFEED has changed its server id from 258 to 45000 <END> Note: there are 44 mins time gap on shrmds2.