You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Q/A][Java SDK (Component)] I'm encountering an issue where the ReconnectTimerTask of the consumer keeps throwing repeated errors after the provider goes offline due to unavailability in the registry
#15878
I am sure that all the content I provide is in English.
Apache Dubbo Component
Java SDK (apache/dubbo)
Details
I'm encountering an issue where the ReconnectTimerTask of the consumer keeps throwing repeated errors after the provider goes offline due to unavailability in the registry: Fail to connect toHeaderExchangeClient
Is there any configuration or method to allow the consumer to automatically remove this instance after multiple failed connection attempts? Otherwise, these Error logs will keep triggering alarms continuously.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Pre-check
Apache Dubbo Component
Java SDK (apache/dubbo)
Details
I'm encountering an issue where the ReconnectTimerTask of the consumer keeps throwing repeated errors after the provider goes offline due to unavailability in the registry:
Fail to connect toHeaderExchangeClientIs there any configuration or method to allow the consumer to automatically remove this instance after multiple failed connection attempts? Otherwise, these Error logs will keep triggering alarms continuously.
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions