-
Notifications
You must be signed in to change notification settings - Fork 1.5k
handle java.util.concurrent.RejectedExecutionException in 7.0.1 #6747
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
2024-12-20 14:00:05,989 [ERROR] io.vertx.core.impl.ContextImpl - Unhandled exception |
This is happening in a different place, but for the same reason. We can simply catch the rejected execution exception in the onClose method. Until it's addressed, these logs can safely be ignored. |
closes: fabric8io#6747 Signed-off-by: Steve Hawkins <[email protected]>
closes: #6747 Signed-off-by: Steve Hawkins <[email protected]>
### What changes were proposed in this pull request? This PR aims to upgrade `kubernetes-client` from 7.0.1 to 7.1.0. ### Why are the changes needed? Keep the dependencies to the latest, and there are some bug fixes in version 7.1.0: - Fix fabric8io/kubernetes-client#6725: (crd-generator) CRD generator missing type for GenericKubernetesResource - Fix fabric8io/kubernetes-client#6747: Preventing websocket error logs when the client is closed - Fix fabric8io/kubernetes-client#6781: Allowing ipv6 entries to work in NO_PROXY - Fix fabric8io/kubernetes-client#6792: VertxHttpClient uses exclusive Vert.x instance by default ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #49925 from wayneguow/kubernetes-client. Authored-by: Wei Guo <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
### What changes were proposed in this pull request? This PR aims to upgrade `kubernetes-client` from 7.0.1 to 7.1.0. ### Why are the changes needed? Keep the dependencies to the latest, and there are some bug fixes in version 7.1.0: - Fix fabric8io/kubernetes-client#6725: (crd-generator) CRD generator missing type for GenericKubernetesResource - Fix fabric8io/kubernetes-client#6747: Preventing websocket error logs when the client is closed - Fix fabric8io/kubernetes-client#6781: Allowing ipv6 entries to work in NO_PROXY - Fix fabric8io/kubernetes-client#6792: VertxHttpClient uses exclusive Vert.x instance by default ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes #49925 from wayneguow/kubernetes-client. Authored-by: Wei Guo <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]> (cherry picked from commit ae2d2e8) Signed-off-by: Dongjoon Hyun <[email protected]>
### What changes were proposed in this pull request? This PR aims to upgrade `kubernetes-client` from 7.0.1 to 7.1.0. ### Why are the changes needed? Keep the dependencies to the latest, and there are some bug fixes in version 7.1.0: - Fix fabric8io/kubernetes-client#6725: (crd-generator) CRD generator missing type for GenericKubernetesResource - Fix fabric8io/kubernetes-client#6747: Preventing websocket error logs when the client is closed - Fix fabric8io/kubernetes-client#6781: Allowing ipv6 entries to work in NO_PROXY - Fix fabric8io/kubernetes-client#6792: VertxHttpClient uses exclusive Vert.x instance by default ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? Pass GA. ### Was this patch authored or co-authored using generative AI tooling? No. Closes apache#49925 from wayneguow/kubernetes-client. Authored-by: Wei Guo <[email protected]> Signed-off-by: Dongjoon Hyun <[email protected]>
Describe the bug
Same issue reported in major version 6.13.3 fixed in 6.13.4 is also occurring 7.0.1
see #6278
Fabric8 Kubernetes Client version
7.0.1
Steps to reproduce
.
Expected behavior
.
Runtime
OpenShift
Kubernetes API Server version
1.25.3@latest
Environment
Linux
Fabric8 Kubernetes Client Logs
Additional context
No response
The text was updated successfully, but these errors were encountered: