[
https://issues.apache.org/jira/browse/IGNITE-26551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Tkalenko updated IGNITE-26551:
-------------------------------------
Description: I discovered that when
*java.util.concurrent.RejectedExecutionException* occurs for pools from
*org.apache.ignite.internal.testframework.ExecutorServiceExtension*, there's
not enough debugging information to better understand the cause of the
exception. I suggest adding the thread prefix name and the pool shutdown stack
trace. (was: I discovered that when
*java.util.concurrent.RejectedExecutionException* occurs for pools from
*org.apache.ignite.internal.testframework.ExecutorServiceExtension*, there's
not enough debugging information to better understand the cause of the
exception. I suggest adding the thread prefix name and the pool stop stack
trace.)
> Expand the information in RejectedExecutionException for pools from
> ExecutorServiceExtension
> --------------------------------------------------------------------------------------------
>
> Key: IGNITE-26551
> URL: https://issues.apache.org/jira/browse/IGNITE-26551
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Tkalenko
> Assignee: Kirill Tkalenko
> Priority: Minor
> Labels: ignite-3
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I discovered that when *java.util.concurrent.RejectedExecutionException*
> occurs for pools from
> *org.apache.ignite.internal.testframework.ExecutorServiceExtension*, there's
> not enough debugging information to better understand the cause of the
> exception. I suggest adding the thread prefix name and the pool shutdown
> stack trace.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
