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

Posted to issues@ignite.apache.org by "Roman Puchkovskiy (Jira)" <ji...@apache.org> on 2025/09/30 12:00:00 UTC

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

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

Roman Puchkovskiy commented on IGNITE-26551:
--------------------------------------------

The patch looks good to me

> 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: 20m
>  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)