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 2018/10/19 14:39:00 UTC

[jira] [Commented] (IGNITE-9948) JettyRestProcessorAuthenticationWithTokenSelfTest.testGetOrCreateCache fails on TC

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

ASF GitHub Bot commented on IGNITE-9948:
----------------------------------------

GitHub user NSAmelchev opened a pull request:

    https://github.com/apache/ignite/pull/5038

    IGNITE-9948

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/NSAmelchev/ignite ignite-9948

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/5038.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 #5038
    
----
commit d2ba064477e45349d4988deb62a70fa8210a48ed
Author: NSAmelchev <ns...@...>
Date:   2018-10-19T14:36:59Z

    For ignite-9948

----


>  JettyRestProcessorAuthenticationWithTokenSelfTest.testGetOrCreateCache fails on TC
> -----------------------------------------------------------------------------------
>
>                 Key: IGNITE-9948
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9948
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Amelchev Nikita
>            Assignee: Amelchev Nikita
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain
>             Fix For: 2.8
>
>
> [Example of fail.|https://ci.ignite.apache.org/viewLog.html?buildId=2118632&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_JavaClient#testNameId-4416495803371140089] Log details:
> {noformat}
> [2018-10-19 06:59:53,063][ERROR][main][root] Test failed.
> java.lang.NullPointerException
> at org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.checkGetOrCreateAndDestroy(JettyRestProcessorAbstractSelfTest.java:593)
> at org.apache.ignite.internal.processors.rest.JettyRestProcessorAbstractSelfTest.testGetOrCreateCache(JettyRestProcessorAbstractSelfTest.java:619)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at org.apache.ignite.testframework.junits.GridAbstractTest.runTestInternal(GridAbstractTest.java:2176)
> at org.apache.ignite.testframework.junits.GridAbstractTest.access$000(GridAbstractTest.java:142)
> at org.apache.ignite.testframework.junits.GridAbstractTest$5.run(GridAbstractTest.java:2091)
> at java.lang.Thread.run(Thread.java:748){noformat}
> The possible reason is the race between getting cache instance on different nodes:
> # Jetty query create cache successfully on one node.
> # PME doesn't have completed.
> # The test fails with NPE while getting the instance of cache on another node.



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