You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Kirill Tkalenko (Jira)" <ji...@apache.org> on 2025/09/30 08:11:00 UTC

[jira] [Created] (IGNITE-26551) Expand the information in RejectedExecutionException for pools from ExecutorServiceExtension

Kirill Tkalenko created IGNITE-26551:
----------------------------------------

             Summary: 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


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.



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