ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Ostanin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-7076) NPE while stopping with GridDhtLockFuture
Date Mon, 26 Mar 2018 10:05:00 GMT

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

Oleg Ostanin commented on IGNITE-7076:
--------------------------------------

I've got several 40+ mb log files from Ignite server nodes where this error message is repeated
constantly for 3 seconds:

[2018-03-25 11:46:43][ERROR][grid-timeout-worker-#39] Error when executing timeout callback:
LockTimeoutObject []
java.lang.NullPointerException: null

.....

[2018-03-25 11:46:46][ERROR][grid-timeout-worker-#39] Error when executing timeout callback:
LockTimeoutObject []
java.lang.

 

Can we fix the issue or at least minimize log output?

 

> NPE while stopping with GridDhtLockFuture
> -----------------------------------------
>
>                 Key: IGNITE-7076
>                 URL: https://issues.apache.org/jira/browse/IGNITE-7076
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: Alexander Belyak
>            Priority: Minor
>
> Get NPE after "Stopped cache" msg
> {noformat}
> 2017-11-29 08:18:20.994 [ERROR][grid-timeout-worker-#119%DPL_GRID%DplGridNodeName%][o.a.i.i.p.t.GridTimeoutProcessor]
Error when executing timeout callback: LockTimeoutObject []
> java.lang.NullPointerException: null
>         at org.apache.ignite.internal.processors.cache.GridCacheContext.loadPreviousValue(GridCacheContext.java:1446)
>         at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.loadMissingFromStore(GridDhtLockFuture.java:1030)
>         at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.onComplete(GridDhtLockFuture.java:731)
>         at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture.access$900(GridDhtLockFuture.java:82)
>         at org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLockFuture$LockTimeoutObject.onTimeout(GridDhtLockFuture.java:1133)
>         at org.apache.ignite.internal.processors.timeout.GridTimeoutProcessor$TimeoutWorker.body(GridTimeoutProcessor.java:163)
>         at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>         at java.lang.Thread.run(Thread.java:748)
> {noformat}
> because in GridCacheContext.java:1446 tryint to read from cacheCfg local variable, but
cacheCfg was zeroed out while cache stopping.
> Probability of such error will be significantly lowered if in GridDhtLockFuture.LockTimeoutObject.onTimeout
we pass actual value of nodeStopping flag (GridGhtLockFuture:1133) instead of hardcoded false.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message