Closed phamtai97 closed 4 years ago
Hi @phamtai97
I guess you set ConsulOptions
's timeout to 10s which is less than blocking awaiting time. In this case, you will receive such errors along with successful events, and this is expected behavior. The bad news: after each timeout error, each next resubscribing will be invoked with a progressive delay (up to 180s).
I believe we should ignore all timeout exceptions with resubscribing without any delay. I'll prepare a patch soon.
Thank you @ruslansennov. I can not set ConsulOptiont's timeout too hight. Because I also call Consul for other APIs.
@ruslansennov Which version did you release?
it will be 4.0.0
But In version > 3.8, Some api of vertx have been changed. I think we only need have patch version such as 3.7.3.
Same issue too. We are using vertx 3.7.1 in production and have to upgrade to version 4.0.0 with a bunch of change is not reasonable. Can you provide a patch version ?
Thank you.
@ruslansennov help me !!!. thanks
@vietj are there any plans to release version 3.8.6?
Oh @ruslansennov , I think that we only need a patch version less V3.8.
i'm afraid it is impossible
cherry-picked to 3.9
branch
cherry-picked to 3.8
branch
Hi @vietj I use the feature to
Watch
key value for my project. Then, I have timeout problem when i watch key-value. I set timeout for a request is 10s. This is error:My code:
Can you help me explain this problem?