Hi,
We received below messages from ADS (159.43.50.22:14002) on 02/06 around 13:24 EST and directory service never recovered and because of it application was not able to make any new subscription at which point we had to manually restart it:
02-06 13:24:13.991 [reuters-session-manager] DirectoryHandler.java:182 [INFO] DirectoryUpdate:
streamId: 2
filter:
Service:
serviceId: 467
[ GroupFilter:
group: 0000: 00 DD ..
status: State: Open/Suspect/None - text: "EaaS*hash4Bstatus-A23: Source has gone down, requesting from another source."
]
02-06 13:24:13.991 [reuters-session-manager] ElektronAdapter.java:387 [INFO] Requested service 'hEDD' is not up. Waiting for service to be up...
02-06 13:24:13.991 [reuters-session-manager] DirectoryHandler.java:175 [INFO] Received Source Directory Update
02-06 13:24:13.991 [reuters-session-manager] DirectoryHandler.java:182 [INFO] DirectoryUpdate:
streamId: 2
filter:
Service:
serviceId: 467
[ GroupFilter:
group: 0000: 00 DE ..
status: State: Open/Suspect/None - text: "EaaS*hash4Bstatus-A23: Source has gone down, requesting from another source."
]
02-06 13:24:13.991 [reuters-session-manager] ElektronAdapter.java:387 [INFO] Requested service 'hEDD' is not up. Waiting for service to be up...
02-06 13:24:13.992 [reuters-session-manager] DirectoryHandler.java:175 [INFO] Received Source Directory Update
02-06 13:24:13.992 [reuters-session-manager] DirectoryHandler.java:182 [INFO] DirectoryUpdate:
streamId: 2
filter:
Service:
serviceId: 467
[ GroupFilter:
group: 0000: 00 5C .\
status: State: Open/Suspect/None - text: "EaaS*hash4Astatus-A23: Source has gone down, requesting from another source."
]
02-06 13:24:13.992 [reuters-session-manager] ElektronAdapter.java:387 [INFO] Requested service 'hEDD' is not up. Waiting for service to be up...
Was there any issue with "159.43.50.22:14002" - ADS over this weekend?
Why source directory service never recovered?
Is there any recommended way of handling this scenario?
Thanks,
Satish