ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Gura <ag...@apache.org>
Subject Re: Pessimistic TXN did not release lock on a key, all subsequent txns failed
Date Mon, 24 Apr 2017 11:41:43 GMT
Hi Binti,

unfortunately I don't have any other ideas why this NPE happens
(except of two mentioned above). But I believe that fix of this
problem will prevent this NPE in all other cases.

About key remaining future: in some cases mentioned NPE led to it.

BTW, did you migrate to Ignite 1.8?


On Fri, Apr 21, 2017 at 10:39 PM, bintisepaha <binti.sepaha@tudor.com> wrote:
> Andrey, we never start a txn on the client side. The key that gets locked on
> our end and stays locked even after a successful txn is never read or
> updated in a txn from the client side. Are you also able to reproduce the
> key remaining locked issue?
>
> Thanks,
> Binti
>
>
>
> --
> View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Pessimistic-TXN-did-not-release-lock-on-a-key-all-subsequent-txns-failed-tp10536p12164.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message