Closed mikefischetti closed 5 months ago
Timer threads cancel after session has been closed and removed from contexts
contexts
Timer threads remain after sessions are closed, increasing the jvm thread count. Timer threads are being created here: https://github.com/Netflix/dgs-framework/blob/38f483fcac83d4932a34ad68d414d6a96b5e2d1b/graphql-dgs-subscriptions-websockets/src/main/kotlin/com/netflix/graphql/dgs/subscriptions/websockets/WebsocketGraphQLTransportWSProtocolHandler.kt#L81
Open a ws connection and send a "connection_init" + "subscribe" message using graphql-transport-ws. A timer thread should have been created. Close the connection and the threads remain.
graphql-transport-ws
opened https://github.com/Netflix/dgs-framework/pull/1808
Expected behavior
Timer threads cancel after session has been closed and removed from
contexts
Actual behavior
Timer threads remain after sessions are closed, increasing the jvm thread count. Timer threads are being created here: https://github.com/Netflix/dgs-framework/blob/38f483fcac83d4932a34ad68d414d6a96b5e2d1b/graphql-dgs-subscriptions-websockets/src/main/kotlin/com/netflix/graphql/dgs/subscriptions/websockets/WebsocketGraphQLTransportWSProtocolHandler.kt#L81
Steps to reproduce
Open a ws connection and send a "connection_init" + "subscribe" message using
graphql-transport-ws
. A timer thread should have been created. Close the connection and the threads remain.