[mapguide-internals] Dangling sockets on un-graceful mgserver shutdown on Linux

[Jackie Ng]

Hi All,

I've been noticing that whenever mgserver ungracefully shuts down whether by
segfault or by being killed off by kill/killall, the TCP/IP ports opened by
MapGuide will not be properly released. Attempting to restart mgserver will
generally fail due to the ports being in use.

The ports will eventually be available after waiting a few minutes after the
un-graceful mgserver shutdown. Is there a way that mgserver can listen for
SIGSEGV and/or SIGKILL (presumably the signals that are raised when such
events happen) and perform any necessary socket clean up before bailing?

- Jackie



--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Dangling-sockets-on-un-graceful-mgserver-shutdown-on-Linux-tp5165499.html
Sent from the MapGuide Internals mailing list archive at Nabble.com.