Binti,
As I see from the thread dumps the node is not stopped because the following
shmem related Thread is trying to acquire a lock preventing the node from
finalization
"ipc-shmem-gc-#24%DataGridServer-Production%" prio=10 tid=0x00007f2124cc4000
nid=0x12cc05 sleeping[0x00007f20fd435000]
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.FileDispatcherImpl.lock0(Native Method)
at sun.nio.ch.FileDispatcherImpl.lock(FileDispatcherImpl.java:89)
at sun.nio.ch.FileChannelImpl.lock(FileChannelImpl.java:982)
at java.nio.channels.FileChannel.lock(FileChannel.java:1052)
at
org.apache.ignite.internal.util.ipc.shmem.IpcSharedMemoryServerEndpoint$GcWorker.cleanupResources(IpcSharedMemoryServerEndpoint.java:608)
at
org.apache.ignite.internal.util.ipc.shmem.IpcSharedMemoryServerEndpoint$GcWorker.body(IpcSharedMemoryServerEndpoint.java:563)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:722)
The file that is being accessed is located in
{ignite_work_dir}/ipc/shmem/lock.file
There is a chance that something happened and the lock wasn’t released by OS on
your side. Please try to clean this directory and let me know the result.
—
Denis
> On Jun 27, 2016, at 5:10 PM, bintisepaha <[email protected]> wrote:
>
> bearrito, in 1.6 we saw streamer hung on flush() or close() and would never
> return. We do not see that issue in 1.5.0.final.
>
> Igniters, could you please look at the earlier attached log files and thread
> dumps to help with the original issue.
>
> Thanks,
> Binti
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/System-exit-not-exiting-cleanly-locked-on-IgnitionEx-IgniteNamedInstance-tp5814p5924.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
