[spsoni]

Hi There,

I have recently started using IceGrid for running my application.

My server application extended CtrlCHandler in C++, therefore, to handle the application termination (graceful server termination, cleaning up some data and threads).

When I manually find server process (automatically started by IceGrid) and kill it using unix kill command (this will invoke CtrlCHandler and invoke clean shutdown of server application), and later IceGrid will restart it. This is expected behaviour and fine.

But, when I stop running server from IceGrid Admin GUI tool, my server seem to be immediately isolated from any further communication and later kill'ed (possibly by kill -9) as I cannot see debug message from CtrlCHandler from my server.

My first curiosity is, how does this "server stop" thing work from IceGrid Admin GUI or in general?

Second, how can I configure IceGrid Admin tool to safely invoke termination of my server application(possibly by just sending Ctrl+C (i mean actual unix function call for it), but not Kill -9 equivalent unix function call.). As, I am missing async callbacks on my client, since IceGrid Admin "server stop" seem to be isolating my server appplication for any message communication first and then killing it. Please explain.

Thanks.