Hi, I've looked at your code.
First of all you have races in your code. For example your start two threads and destroy caches before thread is finished and it leads to cache closed error. Moreover, you stops application before any thread finished and it leads to topology changing and NPE. The second, I don't understand why do you use threads at all? Usually you should start Ignite cluster, connect to it using client node and run scan query. Starting of several instances of Ignite in one JVM makes sense only for test purposes. Anyway, you should start Ignite instances, creates caches and after it run threads with your tasks. On Mon, Dec 12, 2016 at 11:23 AM, Alper Tekinalp <al...@evam.com> wrote: > Hi Andrey. > > Did you able to look to the code? > > Regards. > > On Thu, Dec 8, 2016 at 10:05 AM, Alper Tekinalp <al...@evam.com> wrote: > >> Hi. >> >> Could you please share your reproducer example? >> >> >> I added classes to repoduce the error. It also throws cache closed errors >> I am ok with it. But others. >> >> -- >> Alper Tekinalp >> >> Software Developer >> Evam Streaming Analytics >> >> Atatürk Mah. Turgut Özal Bulv. >> Gardenya 5 Plaza K:6 Ataşehir >> 34758 İSTANBUL >> >> Tel: +90 216 455 01 53 Fax: +90 216 455 01 54 >> www.evam.com.tr >> <http://www.evam.com> >> > > > > -- > Alper Tekinalp > > Software Developer > Evam Streaming Analytics > > Atatürk Mah. Turgut Özal Bulv. > Gardenya 5 Plaza K:6 Ataşehir > 34758 İSTANBUL > > Tel: +90 216 455 01 53 Fax: +90 216 455 01 54 > www.evam.com.tr > <http://www.evam.com>
