Ignite service stops whenever cas.properties is edited

[Mike Kriwonos]

All,

I am running CAS 5.2.6, but have also seen the same behavior in CAS 5.1.x

We are using Apache Ignite integrated with the CAS build for a shared ticket registry and we have two CAS/Ignite nodes. Whenever I open up the cas.properties file in vim Ignite stops on that node and does not restart.  I have to restart tomcat to restart CAS and bring Ignite back online.  Is this by design and if so is there some background for why it functions that way?

Thanks,

Mike