tree b56c3048b75c1e25a9a24790af58cc9920f3e2dc
parent 867558c4589bb61d15ed598648265e42774ce8b8
parent 29e5adfdc446e7b87ac5ecc06dbc71b769e2afc5
author ramangrover29 <ramangrover29@eaa15691-b419-025a-1212-ee371bd00084> 1365137263 +0000
committer ramangrover29 <ramangrover29@eaa15691-b419-025a-1212-ee371bd00084> 1365137263 +0000

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