[
https://issues.apache.org/jira/browse/IGNITE-8436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16475131#comment-16475131
]
Valentin Kulichenko commented on IGNITE-8436:
---------------------------------------------
[~prabhat], you can refer to any test to get general understanding of the test
framework used in Ignite. Should you have any questions - feel free to ask on
the dev@ list.
As for this particular case, I'm not aware of any test that could be used as a
reference. But I think it be fairly straightforward to create one.
> Executor service for services does not shutdown properly
> --------------------------------------------------------
>
> Key: IGNITE-8436
> URL: https://issues.apache.org/jira/browse/IGNITE-8436
> Project: Ignite
> Issue Type: Bug
> Components: managed services
> Reporter: Maxim Muzafarov
> Assignee: Prabhat Ranjan
> Priority: Major
> Labels: newbie
> Fix For: 2.6
>
>
> Issue [IGNITE-4802|https://issues.apache.org/jira/browse/IGNITE-4802]
> introduces us separete thread pool for services execution.
> {{IgniteEx}} class defines a factory for the main Ignite API. It controls
> Grid life cycle and allows listening for grid events.
> As cotributor, you should ensure that execution pool shutdowns properly and
> provide fix if needed in case stop grid instance method call occurs.
> {code:java|title=IgniteEx.java|borderStyle=solid}
> /** Executor service for services. */
> private ThreadPoolExecutor svcExecSvc;
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
