Clone
ramangrover29 <ramangrover29@eaa15691-b419-025a-1212-ee371bd00084>
committed
on 05 Apr 13
Fix for issue: 304 Running 'managix stop' should wait until the asterix instance actually terminates rather than saying the system is stoppe… Show more
Fix for issue: 304 Running 'managix stop' should wait until the asterix instance actually terminates rather than saying the system is stopped prematurely.

What was happening?

A kill -15 is not a force kill and triggers a JVM shutdown hook.

Eventually the hook completes and JVM ends itself. But it may take significant time

if the hoo triggers a potentially expensive operation.

OS would return control to managix tricking it to believe that the script/command finished.

What the fix was?

The script that invoked a kill -15 does not immediately return but waits until it has verified

that the process (JVM) has indeed died. Managix doesnt hear back from the script until

then and so it waits.

git-svn-id: https://asterixdb.googlecode.com/svn/branches/asterix_lsm_stabilization@1502 eaa15691-b419-025a-1212-ee371bd00084

Show less

master + 10 more