Skip to content
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

WatchConnectionManager warning log provides little information #3001

Closed
shawkins opened this issue Apr 15, 2021 · 2 comments
Closed

WatchConnectionManager warning log provides little information #3001

shawkins opened this issue Apr 15, 2021 · 2 comments
Assignees
Milestone

Comments

@shawkins
Copy link
Contributor

We see occurrences of the following:

2021-04-14 03:49:17,302 WARN  [io.fab.kub.cli.dsl.int.WatchConnectionManager] (OkHttp https://172.30.0.1/...) Exec Failure: java.io.EOFException
	at okio.RealBufferedSource.require(RealBufferedSource.java:65)
	at okio.RealBufferedSource.readByte(RealBufferedSource.java:78)
	at okhttp3.internal.ws.WebSocketReader.readHeader(WebSocketReader.java:117)
	at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:101)
	at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:273)
	at okhttp3.internal.ws.RealWebSocket$1.onResponse(RealWebSocket.java:209)
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174)
	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)

But that conveys very little information. Presumably this can happen if the other side drops the websocket connection. Could the message be improved or the stacktrace omitted for EOFExceptions?

@manusa
Copy link
Member

manusa commented May 5, 2021

Relates to #2993

shawkins added a commit to shawkins/kubernetes-client that referenced this issue May 31, 2021
…ions and closure

this localizes the state of a websocket to the listener, rather than the
runner to have a clearer lifecycle.

it also replaces the use of BlockingQueue with CompletableFuture.
shawkins added a commit to shawkins/kubernetes-client that referenced this issue May 31, 2021
…ions and closure

this localizes the state of a websocket to the listener, rather than the
runner to have a clearer lifecycle.

it also replaces the use of BlockingQueue with CompletableFuture.
shawkins added a commit to shawkins/kubernetes-client that referenced this issue May 31, 2021
…ions and closure

this localizes the state of a websocket to the listener, rather than the
runner to have a clearer lifecycle.

it also replaces the use of BlockingQueue with CompletableFuture.
shawkins added a commit to shawkins/kubernetes-client that referenced this issue May 31, 2021
…ions and closure

this localizes the state of a websocket to the listener, rather than the
runner to have a clearer lifecycle.

it also replaces the use of BlockingQueue with CompletableFuture.
shawkins added a commit to shawkins/kubernetes-client that referenced this issue May 31, 2021
…ions and closure

this localizes the state of a websocket to the listener, rather than the
runner to have a clearer lifecycle.

it also replaces the use of BlockingQueue with CompletableFuture.
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Jun 2, 2021
…ions and closure

this localizes the state of a websocket to the listener, rather than the
runner to have a clearer lifecycle.

it also replaces the use of BlockingQueue with CompletableFuture.
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Jun 2, 2021
…ions and closure

this localizes the state of a websocket to the listener, rather than the
runner to have a clearer lifecycle.

it also replaces the use of BlockingQueue with CompletableFuture.
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Jun 2, 2021
…ions and closure

this localizes the state of a websocket to the listener, rather than the
runner to have a clearer lifecycle.

it also replaces the use of BlockingQueue with CompletableFuture.
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Jun 3, 2021
…ions and closure

this localizes the state of a websocket to the listener and removes the
runner abstraction

it also replaces the use of BlockingQueue with CompletableFuture.
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Jun 3, 2021
…ions and closure

this localizes the state of a websocket to the listener and removes the
runner abstraction

it also replaces the use of BlockingQueue with CompletableFuture.
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Jun 3, 2021
…ions and closure

this removes the runner abstraction

it also replaces the use of BlockingQueue with CompletableFuture.
@shawkins shawkins self-assigned this Jun 5, 2021
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Jun 8, 2021
…ions and closure

this removes the runner abstraction

it also replaces the use of BlockingQueue with CompletableFuture.
shawkins added a commit to shawkins/kubernetes-client that referenced this issue Jun 8, 2021
…ions and closure

this removes the runner abstraction

it also replaces the use of BlockingQueue with CompletableFuture.
manusa pushed a commit that referenced this issue Jun 9, 2021
this removes the runner abstraction

it also replaces the use of BlockingQueue with CompletableFuture.
@shawkins
Copy link
Contributor Author

shawkins commented Jun 9, 2021

Closed via #3197

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants