search

yrift / jwebsocket

Automatically exported from code.google.com/p/jwebsocket
0 stars 0 forks source link

Netty issue: "Not releasing all resources" #37

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
If the JWebSocketFactory calls engine.stopEngine e.g. caused by the "shutDown" 
command, apparently not all ressources are released properly, i.e. the 
application does not terminate, possibly due to a remaining running thread or 
similar.

Original issue reported on code.google.com by fivefeetfurther@gmail.com on 9 Aug 2010 at 2:30

GoogleCodeExporter commented 8 years ago 
I already modified the stopEngine method of the NettyEngine to call the 
engineStopped method which at least invokes the engineStopped callbacks of all 
plug-ins to release their resources but apparently that was not yet enough. 
Some things here probably still need to be cleaned up, the application should 
terminate properly (w/o using system.exit ;-)

Original comment by fivefeetfurther@gmail.com on 9 Aug 2010 at 2:30

GoogleCodeExporter commented 8 years ago 
modified the NettyEngine to handle shutdown code specific to netty now the 
server is closed gracefully.

Original comment by mailtopu...@gmail.com on 10 Aug 2010 at 6:45

GoogleCodeExporter commented 8 years ago 
I checked it again and shutting down now works perfectly. Thanks.

Original comment by fivefeetfurther@gmail.com on 10 Aug 2010 at 8:29