Re: Renentrant Lock & deadlock

2017-11-09 Thread Andrey Mashenkov
Hi, ignite.reentrantLock() creates a cache for datastructures dynamically if is not exists yet. So, both it is same issue. On Tue, Oct 31, 2017 at 7:15 PM, rajivgandhi wrote: > That one was with ignite.getOrCreate > This one is with ignite.reentractLock. > > Are the both due to the same defect?

Re: Renentrant Lock & deadlock

2017-10-31 Thread rajivgandhi
That one was with ignite.getOrCreate This one is with ignite.reentractLock. Are the both due to the same defect? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Renentrant Lock & deadlock

2017-10-30 Thread Andrey Mashenkov
Hi Rajiv, Seems, it is same issue as IGNITE-6380. I see tread blocks on dynamic cache for ignite datastructures creation. [1] https://issues.apache.org/jira/browse/IGNITE-6380 On Sat, Oct 28, 2017 at 12:15 AM, rajivgandhi wrote: > Hi, > In line with a deadlock reported earlier >

Renentrant Lock & deadlock

2017-10-27 Thread rajivgandhi
Hi, In line with a deadlock reported earlier , please see below another deadlock scenario, this time with renetrant locks: private void start2() { Ignite ignite = null; try{ ignite = Ignition.start("ignite-deadlock.xml"); IgniteCache cach