[
https://issues.apache.org/jira/browse/IGNITE-11959?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16877962#comment-16877962
]
Ignite TC Bot commented on IGNITE-11959:
----------------------------------------
{panel:title=--> Run :: All: Possible
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Continuous Query 4{color} [[tests
1|https://ci.ignite.apache.org/viewLog.html?buildId=4257146]]
* IgniteCacheQuerySelfTestSuite6:
ContinuousQueryDeserializationErrorOnNodeJoinTest.testDeserializationErrorOnJoiningNode
{color:#d04437}[Check Code Style]{color} [[tests 0 Exit Code
|https://ci.ignite.apache.org/viewLog.html?buildId=4257185]]
{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4257186&buildTypeId=IgniteTests24Java8_RunAll]
> 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)
