I will give that a try to set the port to -1. Could you explain why that might be causing this?
I tried with -DIGNITE_NO_SHUTDOWN_HOOK=true and that lets us exit the process cleanly. This was not an issue for last 6 weeks and it suddenly became an issue for us this week and I am trying to understand what the shared memory port might have to do with this. Thanks, Binti -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/System-exit-not-exiting-cleanly-locked-on-IgnitionEx-IgniteNamedInstance-tp5814p5848.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
