-
Notifications
You must be signed in to change notification settings - Fork 366
event stream being closed error #10498
Copy link
Copy link
Open
Description
Validator *** Error while connecting to beacon node event stream
- probably doesn't need to be an error, its expected that this may disconnect/reconnect occasionally
- depending on how we're setup, might be able to raise an info / warning on disconnect and only error if we can't reconnect for a period of time...
com.launchdarkly.eventsource.StreamClosedByServerException: Stream closed by server
at com.launchdarkly.eventsource.EventParser.getNextChunk(EventParser.java:276)
at com.launchdarkly.eventsource.EventParser.tryNextEvent(EventParser.java:133)
at com.launchdarkly.eventsource.EventParser.nextEvent(EventParser.java:112)
at com.launchdarkly.eventsource.EventSource.requireEvent(EventSource.java:605)
at com.launchdarkly.eventsource.EventSource.readAnyEvent(EventSource.java:397)
at com.launchdarkly.eventsource.background.BackgroundEventSource.pollAndDispatchEvent(BackgroundEventSource.java:194)
at com.launchdarkly.eventsource.background.BackgroundEventSource.access$900(BackgroundEventSource.java:73)
at com.launchdarkly.eventsource.background.BackgroundEventSource$1.run(BackgroundEventSource.java:141)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1583)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels