ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Denis Magda (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3515) NullPointerException when stopping IgniteSemaphore and no method has been called previously to initialize semaphore with initializeSemaphore().
Date Thu, 21 Jul 2016 11:58:20 GMT

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

Denis Magda commented on IGNITE-3515:
-------------------------------------

However the exception is printed out to the logger output, correct? In such a case you can
use {{GridStringLogger}} in the test that will help to check that there is no {{NPE}} when
your fixed is applied. Look for {{GridStringLogger}} usages to see how it's being used in
the tests.

> NullPointerException when stopping IgniteSemaphore and no method has been called previously
to initialize semaphore with initializeSemaphore().
> -----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3515
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3515
>             Project: Ignite
>          Issue Type: Bug
>          Components: data structures
>    Affects Versions: 1.6
>            Reporter: Krome Plasma
>            Assignee: Krome Plasma
>             Fix For: 1.7
>
>
> IgniteSemaphore stop() method does not check if internal synchronization object 'sync'
is null hence null pointer exception is thrown.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message