Websocket container does not provide a way to be shut down

[glassfishrobot]

ContainerProvider.getWebSocketContainer() creates a new instance of WebsocketContainer (the API javadoc specifically says, it has to be a new instance), but WebsocketContainer does not provide any "shut down" method. This causes problems if the instance manages some resources such as executor services, because there is no way how a user can shut down the container and make it release the managed resources.

Affected Versions

[1.1]

[glassfishrobot]

@glassfishrobot Commented
Reported by petrjanouch

[glassfishrobot]

@glassfishrobot Commented
This issue was imported from java.net JIRA WEBSOCKET_SPEC-230

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/websocket-spec/issues/230
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @pavelbucek

[joakime]

This seems to be a duplicate of #212

[markt-asf]

Agreed. Closing as a duplicate.