You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by narges saleh <sn...@gmail.com> on 2021/02/18 23:24:05 UTC
Re: Ignite 2.81. - NULL pointer exception
Was there a resolution for this issue?
On Mon, Sep 7, 2020 at 9:40 AM Ilya Kasnacheev <il...@gmail.com>
wrote:
> Hello!
>
> I wonder why there's no stack traces for all the threads.
>
> I wonder if somebody from the development side will step in (2.8.1):
>
> [05:57:16,193][SEVERE][sys-stripe-15-#16][] Critical system error
> detected. Will be handled accordingly to configured handler
> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
> failureCtx=FailureContext [type=CRITICAL_ERROR,
> err=java.lang.NullPointerException]]
> java.lang.NullPointerException
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:1064)
> // tx is null?
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:953)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:909)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:123)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:217)
> at
> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:215)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
> at
> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1847)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1472)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
> at
> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1367)
> at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at java.lang.Thread.run(Thread.java:745)
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 2 сент. 2020 г. в 11:05, Mahesh Renduchintala <
> mahesh.renduchintala@aline-consulting.com>:
>
>> I sent the logs again. There is no specific activity.
>> We have a cluster - 2 servers and about 15 thick clients
>>
>> Just happened without much info. I can say it is likely a new node joined
>> in and it may have triggered this crash.
>>
>>
>>
Re: Ignite 2.81. - NULL pointer exception
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
I have filed a ticket https://issues.apache.org/jira/browse/IGNITE-13475
Regards,
--
Ilya Kasnacheev
пт, 19 февр. 2021 г. в 02:24, narges saleh <sn...@gmail.com>:
> Was there a resolution for this issue?
>
> On Mon, Sep 7, 2020 at 9:40 AM Ilya Kasnacheev <il...@gmail.com>
> wrote:
>
>> Hello!
>>
>> I wonder why there's no stack traces for all the threads.
>>
>> I wonder if somebody from the development side will step in (2.8.1):
>>
>> [05:57:16,193][SEVERE][sys-stripe-15-#16][] Critical system error
>> detected. Will be handled accordingly to configured handler
>> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
>> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
>> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
>> failureCtx=FailureContext [type=CRITICAL_ERROR,
>> err=java.lang.NullPointerException]]
>> java.lang.NullPointerException
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:1064)
>> // tx is null?
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:953)
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:909)
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:123)
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:217)
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:215)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
>> at
>> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1847)
>> at
>> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1472)
>> at
>> org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
>> at
>> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1367)
>> at
>> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
>> at
>> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> ср, 2 сент. 2020 г. в 11:05, Mahesh Renduchintala <
>> mahesh.renduchintala@aline-consulting.com>:
>>
>>> I sent the logs again. There is no specific activity.
>>> We have a cluster - 2 servers and about 15 thick clients
>>>
>>> Just happened without much info. I can say it is likely a new node
>>> joined in and it may have triggered this crash.
>>>
>>>
>>>
Re: Ignite 2.81. - NULL pointer exception
Posted by Ilya Kasnacheev <il...@gmail.com>.
Hello!
I have filed a ticket https://issues.apache.org/jira/browse/IGNITE-13475
Regards,
--
Ilya Kasnacheev
пт, 19 февр. 2021 г. в 02:24, narges saleh <sn...@gmail.com>:
> Was there a resolution for this issue?
>
> On Mon, Sep 7, 2020 at 9:40 AM Ilya Kasnacheev <il...@gmail.com>
> wrote:
>
>> Hello!
>>
>> I wonder why there's no stack traces for all the threads.
>>
>> I wonder if somebody from the development side will step in (2.8.1):
>>
>> [05:57:16,193][SEVERE][sys-stripe-15-#16][] Critical system error
>> detected. Will be handled accordingly to configured handler
>> [hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
>> super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
>> [SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
>> failureCtx=FailureContext [type=CRITICAL_ERROR,
>> err=java.lang.NullPointerException]]
>> java.lang.NullPointerException
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finishDhtLocal(IgniteTxHandler.java:1064)
>> // tx is null?
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.finish(IgniteTxHandler.java:953)
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.processNearTxFinishRequest(IgniteTxHandler.java:909)
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler.access$200(IgniteTxHandler.java:123)
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:217)
>> at
>> org.apache.ignite.internal.processors.cache.transactions.IgniteTxHandler$3.apply(IgniteTxHandler.java:215)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.processMessage(GridCacheIoManager.java:1142)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.onMessage0(GridCacheIoManager.java:591)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:392)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.handleMessage(GridCacheIoManager.java:318)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager.access$100(GridCacheIoManager.java:109)
>> at
>> org.apache.ignite.internal.processors.cache.GridCacheIoManager$1.onMessage(GridCacheIoManager.java:308)
>> at
>> org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1847)
>> at
>> org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1472)
>> at
>> org.apache.ignite.internal.managers.communication.GridIoManager.access$5200(GridIoManager.java:229)
>> at
>> org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1367)
>> at
>> org.apache.ignite.internal.util.StripedExecutor$Stripe.body(StripedExecutor.java:565)
>> at
>> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> Regards,
>> --
>> Ilya Kasnacheev
>>
>>
>> ср, 2 сент. 2020 г. в 11:05, Mahesh Renduchintala <
>> mahesh.renduchintala@aline-consulting.com>:
>>
>>> I sent the logs again. There is no specific activity.
>>> We have a cluster - 2 servers and about 15 thick clients
>>>
>>> Just happened without much info. I can say it is likely a new node
>>> joined in and it may have triggered this crash.
>>>
>>>
>>>