You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/11/12 12:48:00 UTC
[jira] [Commented] (IGNITE-6802) NullPointerException when WAL
store and WAL archive paths are same
[ https://issues.apache.org/jira/browse/IGNITE-6802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248843#comment-16248843 ]
ASF GitHub Bot commented on IGNITE-6802:
----------------------------------------
GitHub user SomeFire opened a pull request:
https://github.com/apache/ignite/pull/3021
IGNITE-6802
Throwing meaningful exception.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/SomeFire/ignite IGNITE-6802
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3021.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3021
----
commit c12b5b247cfb5c0ea5d45fab2f97fc53cf71da51
Author: Dmitrii Ryabov <so...@gmail.com>
Date: 2017-11-12T12:36:14Z
IGNITE-6802: test
commit d2cd6412d295789c588438950c1e7fa5833e341d
Author: Dmitrii Ryabov <so...@gmail.com>
Date: 2017-11-12T12:38:02Z
IGNITE-6802: throwing meaningful exception
----
> NullPointerException when WAL store and WAL archive paths are same
> -------------------------------------------------------------------
>
> Key: IGNITE-6802
> URL: https://issues.apache.org/jira/browse/IGNITE-6802
> Project: Ignite
> Issue Type: Bug
> Security Level: Public(Viewable by anyone)
> Affects Versions: 2.2
> Reporter: Alexey Kukushkin
> Assignee: Ryabov Dmitrii
> Labels: newbie, usability
> Fix For: 2.4
>
>
> Configuring WAL store and WAL archive paths to be the same results in NullPointerException. We should display a meaningful error about the misconfiguration instead.
> See http://apache-ignite-users.70518.x6.nabble.com/NullPointerException-in-FileWriteAheadLogManager-java-1313-tc17860.html
> The thread includes the reproducer code and stack trace. I was able to reproduce the issue with today's (31-Oct-2017) Apache master.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)