[
https://issues.apache.org/jira/browse/IGNITE-5910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114107#comment-16114107
]
Vyacheslav Daradur commented on IGNITE-5910:
--------------------------------------------
{{ClassCastException}} was fixed by [1'st
commit|https://github.com/apache/ignite/pull/2382/commits/fe0534f41ef994b644ec628435583bc79f0181fd],
and I found one more bug after:
Nodes wich started in separate JVM sometimes couldn't stop properly and were
staying freezed up in OS after test finished.
It relates to the methods: {{#stopAllGrid()}} and {{#stopGrid(name)}} in case
of MultiJVM tests. It was fixed by [2'nd
commit|https://github.com/apache/ignite/pull/2382/commits/4982dba06d5dc7d3c13e74536159164794b857d1].
[Ci.tests|http://ci.ignite.apache.org/viewLog.html?buildId=755961]
> 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
> Fix For: 2.2
>
>
> {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}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
