You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Kartik Somani (Jira)" <ji...@apache.org> on 2020/06/08 06:52:00 UTC

[jira] [Comment Edited] (IGNITE-13128) IgniteLock throws NullPointerException when removed before use

    [ https://issues.apache.org/jira/browse/IGNITE-13128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17127939#comment-17127939 ] 

Kartik Somani edited comment on IGNITE-13128 at 6/8/20, 6:51 AM:
-----------------------------------------------------------------

[~isapego] So I'm thinking of throwing IllegalStateException (assuming attempting to lock after it has been closed is an illegal state).

Can you confirm if this is correct behavior?


was (Author: kay_jpr):
So I'm thinking of throwing IllegalStateException (assuming attempting to lock after it has been closed is an illegal state).

Can you confirm if this is correct behavior?

> IgniteLock throws NullPointerException when removed before use
> --------------------------------------------------------------
>
>                 Key: IGNITE-13128
>                 URL: https://issues.apache.org/jira/browse/IGNITE-13128
>             Project: Ignite
>          Issue Type: Bug
>          Components: data structures
>    Affects Versions: 2.8
>            Reporter: Pavel Tupitsyn
>            Assignee: Kartik Somani
>            Priority: Major
>              Labels: newbie
>             Fix For: 2.9
>
>
> Reproducer: 
> {code:java}
>     public void testClosedLockThrowsIgniteException() {
>         final String lockName = "testRemovedLockThrowsIgniteException";
>         Ignite srv = ignite(0);
>         IgniteLock lock1 = srv.reentrantLock(lockName, false, false, true);
>         IgniteLock lock2 = srv.reentrantLock(lockName, false, false, true);
>         lock1.close();
>         lock2.lock();
>     }
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)