[jira] [Resolved] (IGNITE-12570) What is the root cause of IgniteCheckedException: Invalid handshake message
[ https://issues.apache.org/jira/browse/IGNITE-12570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin resolved IGNITE-12570. - Resolution: Not A Bug > What is the root cause of IgniteCheckedException: Invalid handshake message > --- > > Key: IGNITE-12570 > URL: https://issues.apache.org/jira/browse/IGNITE-12570 > Project: Ignite > Issue Type: Bug > Components: examples >Affects Versions: 2.7.5 >Reporter: shubhendra sen >Priority: Major > > Two environments are there. On one environment ignite servers are working > properly. but on the other environment i am getting an exception. > > ** > Closing NIO session because of unhandled exception. > org.apache.ignite.IgniteCheckedException: Invalid handshake message > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioServerBuffer.read(ClientListenerNioServerBuffer.java:114) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:59) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:39) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:113) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:108) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3575) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:174) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1150) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2411) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2178) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1819) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na] > > So i have two Questions. > 1) What could be the possible causes of this exception ?. and > 2)What re the solutions. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Reopened] (IGNITE-12570) What is the root cause of IgniteCheckedException: Invalid handshake message
[ https://issues.apache.org/jira/browse/IGNITE-12570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan Pavlukhin reopened IGNITE-12570: - Ignite Flags: (was: Docs Required,Release Notes Required) > What is the root cause of IgniteCheckedException: Invalid handshake message > --- > > Key: IGNITE-12570 > URL: https://issues.apache.org/jira/browse/IGNITE-12570 > Project: Ignite > Issue Type: Bug > Components: examples >Affects Versions: 2.7.5 >Reporter: shubhendra sen >Priority: Major > > Two environments are there. On one environment ignite servers are working > properly. but on the other environment i am getting an exception. > > ** > Closing NIO session because of unhandled exception. > org.apache.ignite.IgniteCheckedException: Invalid handshake message > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioServerBuffer.read(ClientListenerNioServerBuffer.java:114) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:59) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:39) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:113) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:108) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3575) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:174) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1150) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2411) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2178) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1819) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na] > > So i have two Questions. > 1) What could be the possible causes of this exception ?. and > 2)What re the solutions. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (IGNITE-12570) What is the root cause of IgniteCheckedException: Invalid handshake message
[ https://issues.apache.org/jira/browse/IGNITE-12570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] shubhendra sen resolved IGNITE-12570. - Release Note: Make sure only ignite applications are hitting the ignite ports. If other applications hit the ignite port then this exception will persist. Resolution: Fixed > What is the root cause of IgniteCheckedException: Invalid handshake message > --- > > Key: IGNITE-12570 > URL: https://issues.apache.org/jira/browse/IGNITE-12570 > Project: Ignite > Issue Type: Bug > Components: examples >Affects Versions: 2.7.5 >Reporter: shubhendra sen >Priority: Major > > Two environments are there. On one environment ignite servers are working > properly. but on the other environment i am getting an exception. > > ** > Closing NIO session because of unhandled exception. > org.apache.ignite.IgniteCheckedException: Invalid handshake message > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioServerBuffer.read(ClientListenerNioServerBuffer.java:114) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:59) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:39) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:113) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:108) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3575) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:174) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1150) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2411) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2178) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1819) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na] > > So i have two Questions. > 1) What could be the possible causes of this exception ?. and > 2)What re the solutions. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12570) What is the root cause of IgniteCheckedException: Invalid handshake message
[ https://issues.apache.org/jira/browse/IGNITE-12570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024130#comment-17024130 ] shubhendra sen commented on IGNITE-12570: - Thanks guys for assisting me. As you said some other application was trying to hit the ignite ports. Issue resolved. > What is the root cause of IgniteCheckedException: Invalid handshake message > --- > > Key: IGNITE-12570 > URL: https://issues.apache.org/jira/browse/IGNITE-12570 > Project: Ignite > Issue Type: Bug > Components: examples >Affects Versions: 2.7.5 >Reporter: shubhendra sen >Priority: Major > > Two environments are there. On one environment ignite servers are working > properly. but on the other environment i am getting an exception. > > ** > Closing NIO session because of unhandled exception. > org.apache.ignite.IgniteCheckedException: Invalid handshake message > at > org.apache.ignite.internal.processors.odbc.ClientListenerNioServerBuffer.read(ClientListenerNioServerBuffer.java:114) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:59) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.processors.odbc.ClientListenerBufferedParser.decode(ClientListenerBufferedParser.java:39) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioCodecFilter.onMessageReceived(GridNioCodecFilter.java:113) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:108) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$HeadFilter.onMessageReceived(GridNioServer.java:3575) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioFilterChain.onMessageReceived(GridNioFilterChain.java:174) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$ByteBufferNioClientWorker.processRead(GridNioServer.java:1150) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.processSelectedKeysOptimized(GridNioServer.java:2411) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:2178) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1819) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at > org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:119) > ~[ignite-core-8.7.5.jar!/:8.7.5] > at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na] > > So i have two Questions. > 1) What could be the possible causes of this exception ?. and > 2)What re the solutions. > > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12470) Pme-free switch feature should be deactivatable
[ https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024120#comment-17024120 ] Anton Vinogradov commented on IGNITE-12470: --- Merged to master branch. > Pme-free switch feature should be deactivatable > --- > > Key: IGNITE-12470 > URL: https://issues.apache.org/jira/browse/IGNITE-12470 > Project: Ignite > Issue Type: Task >Reporter: Anton Vinogradov >Assignee: Anton Vinogradov >Priority: Blocker > Labels: newbie > Fix For: 2.8, 2.9 > > Time Spent: 5h 10m > Remaining Estimate: 0h > > We should be able to disable this feature by some env/jvm property. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (IGNITE-12470) Pme-free switch feature should be deactivatable
[
https://issues.apache.org/jira/browse/IGNITE-12470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024116#comment-17024116
]
Ignite TC Bot commented on IGNITE-12470:
{panel:title=Branch: [pull/7304/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4957003&buildTypeId=IgniteTests24Java8_RunAll]
> Pme-free switch feature should be deactivatable
> ---
>
> Key: IGNITE-12470
> URL: https://issues.apache.org/jira/browse/IGNITE-12470
> Project: Ignite
> Issue Type: Task
>Reporter: Anton Vinogradov
>Assignee: Anton Vinogradov
>Priority: Blocker
> Labels: newbie
> Fix For: 2.8, 2.9
>
> Time Spent: 5h
> Remaining Estimate: 0h
>
> We should be able to disable this feature by some env/jvm property.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (IGNITE-12554) Ignite instance couldn't be restarted if it's parent thread group has been called destroy once
[
https://issues.apache.org/jira/browse/IGNITE-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin updated IGNITE-12554:
Fix Version/s: 2.9
> Ignite instance couldn't be restarted if it's parent thread group has been
> called destroy once
> --
>
> Key: IGNITE-12554
> URL: https://issues.apache.org/jira/browse/IGNITE-12554
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7.6
>Reporter: ha faculty
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.9
>
> Attachments: NodeRestartTesting.java
>
>
> I am using an inhouse platform which manage the life cycle of ignite instance
> by calling ignition.start() and ignition.stop() from a web application.
> it could be started without issue for the first time. however, if it stop the
> ignite by calling ignition.stop() and followed by destroying the parent
> thread group which starting it.
> Calling ignition.start() in the 2nd time will throw the following exception
> Exception in thread "kickOff" java.lang.IllegalThreadStateExceptionException
> in thread "kickOff" java.lang.IllegalThreadStateException at
> java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:867) at
> java.lang.Thread.init(Thread.java:405) at
> java.lang.Thread.init(Thread.java:349) at
> java.lang.Thread.(Thread.java:599) at
> org.apache.ignite.thread.IgniteThread.(IgniteThread.java:96) at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.start(StripedExecutor.java:474)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:121)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:80)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1842)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:565) at
> org.apache.ignite.Ignition.start(Ignition.java:305) at
> com.faculty.poc.ignite.app.NodeRestartTesting.run(NodeRestartTesting.java:60)
> at java.lang.Thread.run(Thread.java:748)
> Please find my demo code for this issue.
> Walk through into Ignite code, it should be caused by a static thread group
> created in IgniteThread class. (private static final ThreadGroup DFLT_GRP =
> new ThreadGroup("ignite")
> Destroyed the parent thread group which start the ignite instance will result
> in causing the DFLT_GRP go into destroyed state. Therefore, when Ignite was
> start ifor the 2nd time, this static thread group has been destroyed and no
> longer able to run the ignite.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Comment Edited] (IGNITE-12554) Ignite instance couldn't be restarted if it's parent thread group has been called destroy once
[
https://issues.apache.org/jira/browse/IGNITE-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024104#comment-17024104
]
Ivan Pavlukhin edited comment on IGNITE-12554 at 1/27/20 6:23 AM:
--
I raised [PR|https://github.com/apache/ignite/pull/7297] removing special
ThreadGroup.
was (Author: pavlukhin):
I raised (PR|https://github.com/apache/ignite/pull/7297) removing special
ThreadGroup.
> Ignite instance couldn't be restarted if it's parent thread group has been
> called destroy once
> --
>
> Key: IGNITE-12554
> URL: https://issues.apache.org/jira/browse/IGNITE-12554
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7.6
>Reporter: ha faculty
>Assignee: Ivan Pavlukhin
>Priority: Major
> Attachments: NodeRestartTesting.java
>
>
> I am using an inhouse platform which manage the life cycle of ignite instance
> by calling ignition.start() and ignition.stop() from a web application.
> it could be started without issue for the first time. however, if it stop the
> ignite by calling ignition.stop() and followed by destroying the parent
> thread group which starting it.
> Calling ignition.start() in the 2nd time will throw the following exception
> Exception in thread "kickOff" java.lang.IllegalThreadStateExceptionException
> in thread "kickOff" java.lang.IllegalThreadStateException at
> java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:867) at
> java.lang.Thread.init(Thread.java:405) at
> java.lang.Thread.init(Thread.java:349) at
> java.lang.Thread.(Thread.java:599) at
> org.apache.ignite.thread.IgniteThread.(IgniteThread.java:96) at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.start(StripedExecutor.java:474)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:121)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:80)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1842)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:565) at
> org.apache.ignite.Ignition.start(Ignition.java:305) at
> com.faculty.poc.ignite.app.NodeRestartTesting.run(NodeRestartTesting.java:60)
> at java.lang.Thread.run(Thread.java:748)
> Please find my demo code for this issue.
> Walk through into Ignite code, it should be caused by a static thread group
> created in IgniteThread class. (private static final ThreadGroup DFLT_GRP =
> new ThreadGroup("ignite")
> Destroyed the parent thread group which start the ignite instance will result
> in causing the DFLT_GRP go into destroyed state. Therefore, when Ignite was
> start ifor the 2nd time, this static thread group has been destroyed and no
> longer able to run the ignite.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12554) Ignite instance couldn't be restarted if it's parent thread group has been called destroy once
[
https://issues.apache.org/jira/browse/IGNITE-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024104#comment-17024104
]
Ivan Pavlukhin commented on IGNITE-12554:
-
I raised (PR|https://github.com/apache/ignite/pull/7297) removing special
ThreadGroup.
> Ignite instance couldn't be restarted if it's parent thread group has been
> called destroy once
> --
>
> Key: IGNITE-12554
> URL: https://issues.apache.org/jira/browse/IGNITE-12554
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7.6
>Reporter: ha faculty
>Assignee: Ivan Pavlukhin
>Priority: Major
> Attachments: NodeRestartTesting.java
>
>
> I am using an inhouse platform which manage the life cycle of ignite instance
> by calling ignition.start() and ignition.stop() from a web application.
> it could be started without issue for the first time. however, if it stop the
> ignite by calling ignition.stop() and followed by destroying the parent
> thread group which starting it.
> Calling ignition.start() in the 2nd time will throw the following exception
> Exception in thread "kickOff" java.lang.IllegalThreadStateExceptionException
> in thread "kickOff" java.lang.IllegalThreadStateException at
> java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:867) at
> java.lang.Thread.init(Thread.java:405) at
> java.lang.Thread.init(Thread.java:349) at
> java.lang.Thread.(Thread.java:599) at
> org.apache.ignite.thread.IgniteThread.(IgniteThread.java:96) at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.start(StripedExecutor.java:474)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:121)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:80)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1842)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:565) at
> org.apache.ignite.Ignition.start(Ignition.java:305) at
> com.faculty.poc.ignite.app.NodeRestartTesting.run(NodeRestartTesting.java:60)
> at java.lang.Thread.run(Thread.java:748)
> Please find my demo code for this issue.
> Walk through into Ignite code, it should be caused by a static thread group
> created in IgniteThread class. (private static final ThreadGroup DFLT_GRP =
> new ThreadGroup("ignite")
> Destroyed the parent thread group which start the ignite instance will result
> in causing the DFLT_GRP go into destroyed state. Therefore, when Ignite was
> start ifor the 2nd time, this static thread group has been destroyed and no
> longer able to run the ignite.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Assigned] (IGNITE-12554) Ignite instance couldn't be restarted if it's parent thread group has been called destroy once
[
https://issues.apache.org/jira/browse/IGNITE-12554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Pavlukhin reassigned IGNITE-12554:
---
Assignee: Ivan Pavlukhin
> Ignite instance couldn't be restarted if it's parent thread group has been
> called destroy once
> --
>
> Key: IGNITE-12554
> URL: https://issues.apache.org/jira/browse/IGNITE-12554
> Project: Ignite
> Issue Type: Bug
> Components: cache
>Affects Versions: 2.7.6
>Reporter: ha faculty
>Assignee: Ivan Pavlukhin
>Priority: Major
> Attachments: NodeRestartTesting.java
>
>
> I am using an inhouse platform which manage the life cycle of ignite instance
> by calling ignition.start() and ignition.stop() from a web application.
> it could be started without issue for the first time. however, if it stop the
> ignite by calling ignition.stop() and followed by destroying the parent
> thread group which starting it.
> Calling ignition.start() in the 2nd time will throw the following exception
> Exception in thread "kickOff" java.lang.IllegalThreadStateExceptionException
> in thread "kickOff" java.lang.IllegalThreadStateException at
> java.lang.ThreadGroup.addUnstarted(ThreadGroup.java:867) at
> java.lang.Thread.init(Thread.java:405) at
> java.lang.Thread.init(Thread.java:349) at
> java.lang.Thread.(Thread.java:599) at
> org.apache.ignite.thread.IgniteThread.(IgniteThread.java:96) at
> org.apache.ignite.internal.util.StripedExecutor$Stripe.start(StripedExecutor.java:474)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:121)
> at
> org.apache.ignite.internal.util.StripedExecutor.(StripedExecutor.java:80)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1842)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1730)
> at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1158) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:589) at
> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:565) at
> org.apache.ignite.Ignition.start(Ignition.java:305) at
> com.faculty.poc.ignite.app.NodeRestartTesting.run(NodeRestartTesting.java:60)
> at java.lang.Thread.run(Thread.java:748)
> Please find my demo code for this issue.
> Walk through into Ignite code, it should be caused by a static thread group
> created in IgniteThread class. (private static final ThreadGroup DFLT_GRP =
> new ThreadGroup("ignite")
> Destroyed the parent thread group which start the ignite instance will result
> in causing the DFLT_GRP go into destroyed state. Therefore, when Ignite was
> start ifor the 2nd time, this static thread group has been destroyed and no
> longer able to run the ignite.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12574) Fix failing IoStatisticsBasicIndexSelfTest
[
https://issues.apache.org/jira/browse/IGNITE-12574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17024091#comment-17024091
]
Ignite TC Bot commented on IGNITE-12574:
{panel:title=Branch: [pull/7303/head] Base: [master] : No blockers
found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--> Run :: All*
Results|https://ci.ignite.apache.org/viewLog.html?buildId=4956754&buildTypeId=IgniteTests24Java8_RunAll]
> Fix failing IoStatisticsBasicIndexSelfTest
> --
>
> Key: IGNITE-12574
> URL: https://issues.apache.org/jira/browse/IGNITE-12574
> Project: Ignite
> Issue Type: Bug
> Components: sql
>Reporter: Ivan Pavlukhin
>Assignee: Ivan Pavlukhin
>Priority: Major
> Fix For: 2.9
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Need to move
> org.apache.ignite.internal.processors.cache.index.IoStatisticsBasicIndexSelfTest
> into a test suite with enabled persistence.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (IGNITE-12398) Apache Ignite Cluster(Amazon S3 Based Discovery) Nodes getting down if we connect Ignite Visor Command Line Interface
[
https://issues.apache.org/jira/browse/IGNITE-12398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023916#comment-17023916
]
Emmanouil Gkatziouras commented on IGNITE-12398:
Hi [~ravimsc] I try to reproduce the issue but I am not successful.
I create a cluster of 3 on AWS.
I add the configuration for the S3 discovery.
{code:java}
http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd";>
{code}
Then I ssh to one machine and connect using Visor.
May I ask for your Ignite configuration?
> Apache Ignite Cluster(Amazon S3 Based Discovery) Nodes getting down if we
> connect Ignite Visor Command Line Interface
> -
>
> Key: IGNITE-12398
> URL: https://issues.apache.org/jira/browse/IGNITE-12398
> Project: Ignite
> Issue Type: Bug
> Components: aws, general, s3, visor
>Affects Versions: 2.7
> Environment: Production
>Reporter: Ravi Kumar Powli
>Assignee: Emmanouil Gkatziouras
>Priority: Blocker
> Fix For: None, 2.8
>
>
> We have Apache Ignite 3 node cluster setup with Amazon S3 Based Discovery. If
> we connect any one cluster node using Ignite Visor Command Line Interface it
> got hang and automatically cluster nodes(all the three nodes) are going down.
> Please find the below exception stacktrace.
> [SEVERE][tcp-disco-msg-worker-#2%DataStoreIgniteCache%][] Critical system
> error detected. Will be handled accordingly to configured handler
> [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=java.lang.NullPointerException]]
> java.lang.NullPointerException
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.key(TcpDiscoveryS3IpFinder.java:247)
> at
> org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder.registerAddresses(TcpDiscoveryS3IpFinder.java:205)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddFinishedMessage(ServerImpl.java:4616)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processNodeAddedMessage(ServerImpl.java:4232)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2816)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2611)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorker.body(ServerImpl.java:7188)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2700)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7119)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [10:36:54,600][SEVERE][tcp-disco-msg-worker-#2%DataStoreIgniteCache%][]
> Critical system error detected. Will be handled accordingly to configured
> handler [hnd=NoOpFailureHandler [super=AbstractFailureHandler
> [ignoredFailureTypes=[SYSTEM_WORKER_BLOCKED]]], failureCtx=FailureContext
> [type=SYSTEM_WORKER_TERMINATION, err=class o.a.i.IgniteException: GridWorker
> [name=tcp-disco-msg-worker, igniteInstanceName=DataStoreIgniteCache,
> finished=true, heartbeatTs=1574332614423]]]
> class org.apache.ignite.IgniteException: GridWorker
> [name=tcp-disco-msg-worker, igniteInstanceName=DataStoreIgniteCache,
> finished=true, heartbeatTs=1574332614423]
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1831)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance$2.apply(IgnitionEx.java:1826)
> at
> org.apache.ignite.internal.worker.WorkersRegistry.onStopped(WorkersRegistry.java:169)
> at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:153)
> at
> org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerThread.body(ServerImpl.java:7119)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> [10:36:59] Ignite node stopped OK [name=DataStoreIgniteCache,
> uptime=00:01:13.934]
--
This message wa
[jira] [Commented] (IGNITE-12448) Calcite integration. Communication protocol.
[ https://issues.apache.org/jira/browse/IGNITE-12448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17023780#comment-17023780 ] Roman Kondakov commented on IGNITE-12448: - [~gvvinblade], overall patch looks good for me. I left several minor comments in PR. > Calcite integration. Communication protocol. > > > Key: IGNITE-12448 > URL: https://issues.apache.org/jira/browse/IGNITE-12448 > Project: Ignite > Issue Type: Task > Components: sql >Reporter: Igor Seliverstov >Assignee: Igor Seliverstov >Priority: Major > Time Spent: 2.5h > Remaining Estimate: 0h > > We need to introduce a communication protocol between query fragments in > scope of query execution. > * Protocol should have Push semantics with back pressure ability > * Protocol have to provide ordering guaranties - the data batches processed > in same order they sent to remote node. > * Protocol have to provide delivery guaranties. -- This message was sent by Atlassian Jira (v8.3.4#803005)
