[
https://issues.apache.org/jira/browse/IGNITE-13722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-13722:
------------------------------------
Description:
It's needed to close Ignite thin/thick client that is used by Spring Data for
accessing the Ignite cluster when closing Spring context.
Currently, if Ignite/ClientConfiguration is used to configure Ignite cluster
access for a repository (see RepositoryConfig), instances of
Ignite/IgniteClient remains unclosed after the close of Spring context.
To solve this issue it's proposed to move management of Ignite instances needed
by Spring Data for accessing the cluster to separate configurable factory
bean. It will be auto-registered by Spring Data and will close all Ignite
resources when closing the Spring context.
was:
It's needed to close Ignite thin/thick client that is used by Spring Data for
accessing the Ignite cluster when closing Spring context.
Currently, if Ignite/ClientConfiguration is used to configure Ignite cluster
access for a repository (see RepositoryConfig), instances of
Ignite/IgniteClient remains unclosed after the close of Spring context.
To solve this issue it's proposed to move management of Ignite instances needed
by Spring Data for accessing the cluster to separate configurable bean. It
will be auto-registered by Spring Data and will close all Ignite resources when
closing the Spring context.
> Ignite Spring Data: Ignite resources are not closed properly when closing
> Spring context.
> -----------------------------------------------------------------------------------------
>
> Key: IGNITE-13722
> URL: https://issues.apache.org/jira/browse/IGNITE-13722
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
>
> It's needed to close Ignite thin/thick client that is used by Spring Data for
> accessing the Ignite cluster when closing Spring context.
> Currently, if Ignite/ClientConfiguration is used to configure Ignite cluster
> access for a repository (see RepositoryConfig), instances of
> Ignite/IgniteClient remains unclosed after the close of Spring context.
> To solve this issue it's proposed to move management of Ignite instances
> needed by Spring Data for accessing the cluster to separate configurable
> factory bean. It will be auto-registered by Spring Data and will close all
> Ignite resources when closing the Spring context.
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
