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

Ivan Daschinsky commented on IGNITE-26959:
------------------------------------------

According to log
{code}
2: [m org.apache.ignite.IgniteException: Failed to stop continuous query (node 
is stopping)
04:01:28  2: at 
org.apache.ignite.internal.util.CommonUtils.convertException(CommonUtils.java:2112)
 [classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl$6.close(IgniteCacheProxyImpl.java:716)
 ~[classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.processors.platform.client.cache.ClientCacheQueryContinuousHandle.close(ClientCacheQueryContinuousHandle.java:89)
 ~[classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.processors.platform.client.ClientResourceRegistry.closeIfNeeded(ClientResourceRegistry.java:99)
 ~[classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.processors.platform.client.ClientResourceRegistry.clean(ClientResourceRegistry.java:89)
 ~[classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.processors.platform.client.ClientConnectionContext.onDisconnected(ClientConnectionContext.java:248)
 ~[classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onDisconnected(ClientListenerNioListener.java:166)
 ~[classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onSessionClosed(GridNioFilterChain.java:257)
 ~[classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedSessionClosed(GridNioFilterAdapter.java:96)
 ~[classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$2.body(GridNioAsyncNotifyFilter.java:83)
 ~[classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:125) 
[classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
 [classes/:?]
04:01:28  2: at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
 [?:?]
04:01:28  2: at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
 [?:?]
04:01:28  2: at java.base/java.lang.Thread.run(Thread.java:833) [?:?]
04:01:28  2: Caused by: org.apache.ignite.internal.NodeStoppingException: 
Failed to stop continuous query (node is stopping)
04:01:28  2: at 
org.apache.ignite.internal.processors.continuous.GridContinuousProcessor.stopRoutine(GridContinuousProcessor.java:1071)
 ~[classes/:?]
04:01:28  2: at 
org.apache.ignite.internal.processors.cache.IgniteCacheProxyImpl$6.close(IgniteCacheProxyImpl.java:713)
 ~[classes/:?]
{code}

I suppose that current implementation of resource cleaning is incorrect, we 
should log error and continue with other resources, we shouldn't stop the 
iteration. 
So the best approach is just to refactor a little bit the code, and don't 
forget to decrement resource counter in finally block

> Test TestLongEventsProcessingDisconnect from C++ test suite is broken in 
> master
> -------------------------------------------------------------------------------
>
>                 Key: IGNITE-26959
>                 URL: https://issues.apache.org/jira/browse/IGNITE-26959
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Sergey Chugunov
>            Priority: Major
>              Labels: ise
>             Fix For: 2.18
>
>
> According to 
> [history|https://ci2.ignite.apache.org/project.html?projectId=IgniteTests24Java8&testNameId=-5112321148966502234&tab=testDetails&branch_IgniteTests24Java8=%3Cdefault%3E]
>  this test is broken in master branch since 22 October 2025.
> One possible culprit is a [refactoring 
> commit|https://github.com/apache/ignite/commit/0b5b218254dd49695e83ea1baa1319ffabc6ffa0#diff-37f047534e3320d3378962125b64f64028d3e51a25c694d66e83ea84f49b55df]
>  that broke behavior of catching exceptions when cleaning up resources, but 
> more investigation is needed.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to