ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirill Tkalenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11959) NullPointerException If transaction failed and failure handler doesn't configured explicitly
Date Thu, 04 Jul 2019 06:16:00 GMT

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

Kirill Tkalenko commented on IGNITE-11959:
------------------------------------------

My changes don't brake tests above.

> NullPointerException If transaction failed and failure handler doesn't configured explicitly
> --------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-11959
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11959
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Kirill Tkalenko
>            Assignee: Kirill Tkalenko
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In IGNITE-9082 was introduced code in IgniteTxAdapter:
> {code:java}
>             U.error(log, String.format(fmt, commit, CU.txString(this),
>                 cctx.gridConfig().getFailureHandler().getClass().getSimpleName()), e);
> {code}
> We get NullPointerException, If failureHander doesn't configured explicitly.
> Information about configured failureHandler is printed in FailureProcessor logic. I think
we could remove failureHandler classname from such log messages.



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

Mime
View raw message