You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Daradur (JIRA)" <ji...@apache.org> on 2018/03/15 16:03:00 UTC

[jira] [Commented] (IGNITE-5910) Method stopGrid(name) doesn't work in multiJvm mode

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

Vyacheslav Daradur commented on IGNITE-5910:
--------------------------------------------

[~dpavlov], thank you for the notes, it's fixed now.

> Method stopGrid(name) doesn't work in multiJvm mode
> ---------------------------------------------------
>
>                 Key: IGNITE-5910
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5910
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.1
>            Reporter: Vyacheslav Daradur
>            Assignee: Vyacheslav Daradur
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain, tests
>             Fix For: 2.5
>
>
> {code:title=Exception at call}
> java.lang.ClassCastException: org.apache.ignite.testframework.junits.multijvm.IgniteProcessProxy cannot be cast to org.apache.ignite.internal.IgniteKernal
> {code}
> {code:title=Reproducer snippet}
>     /** {@inheritDoc} */
>     @Override protected boolean isMultiJvm() {
>         return true;
>     }
>     /**
>      * @throws Exception If failed.
>      */
>     public void testGrid() throws Exception {
>         try {
>             startGrid(0);
>             startGrid(1);
>         }
>         finally {
>             stopGrid(1);
>             stopGrid(0);
>         }
>     }
> {code}
> *UPD:* It is necessary to fix possibility of hangup of a system thread of separate JVM at Ignite's node shutdown.



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