Hello By IgniteClient, I meant the starting Ignite in a client mode which interacts with Ignite program in a server mode. A typical Client-Server architecture.I may not be able to recreate it but I can mention the sequence of events which led to the same. Please allow me a day's time for the same.
When I looked at the heap dump, I could see a huge number of GridFutureAdapter$Node objects which were created and since the streamer wasn't able to flush them therefore they remained in the heap causing the heap to choke and triggering a FULL GC in vain. Now since the ignite.close method was not able to complete because it was blocked, the GC wasn't able to clear the GridFutureAdapter$Node objects. I will try your suggestion on a timeout but as I mentioned creating that scenario will be difficult. Regards -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
