You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Tupitsyn (JIRA)" <ji...@apache.org> on 2017/04/05 05:30:41 UTC
[jira] [Updated] (IGNITE-4856) .NET: StopAll on AppDomain unload
[ https://issues.apache.org/jira/browse/IGNITE-4856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Tupitsyn updated IGNITE-4856:
-----------------------------------
Description:
In certain scenarios .NET {{AppDomain}} can be unloaded and started again. Java part of Ignite continues to run, but .NET part (including Ignite instances) is lost. User can no longer work with started nodes, .NET callback pointers are lost, etc.
1) Track AppDomain unload and stop all Ignite instances.
2) When starting Ignite, wait for node with specified name to stop.
3) Make it possible to auto-generate a unique grid name automatically? This may be useful in app.config.
IIS issues example: http://stackoverflow.com/questions/42961879/how-do-i-retrieve-a-started-ignite-instance-when-a-website-restart-occurs-in-iis/42968183#42968183
was:
In certain scenarios .NET {{AppDomain}} can be unloaded and started again. Java part of Ignite continues to run, but .NET part (including Ignite instances) is lost. User can no longer work with started nodes, .NET callback pointers are lost, etc.
1) Track AppDomain unload and stop all Ignite instances.
2) When starting Ignite, wait for node with specified name to stop.
3) Make it possible to auto-generate a unique grid name automatically?
IIS issues example: http://stackoverflow.com/questions/42961879/how-do-i-retrieve-a-started-ignite-instance-when-a-website-restart-occurs-in-iis/42968183#42968183
> .NET: StopAll on AppDomain unload
> ---------------------------------
>
> Key: IGNITE-4856
> URL: https://issues.apache.org/jira/browse/IGNITE-4856
> Project: Ignite
> Issue Type: Improvement
> Components: platforms
> Affects Versions: 1.6
> Reporter: Pavel Tupitsyn
> Labels: .NET
> Fix For: 2.0
>
>
> In certain scenarios .NET {{AppDomain}} can be unloaded and started again. Java part of Ignite continues to run, but .NET part (including Ignite instances) is lost. User can no longer work with started nodes, .NET callback pointers are lost, etc.
> 1) Track AppDomain unload and stop all Ignite instances.
> 2) When starting Ignite, wait for node with specified name to stop.
> 3) Make it possible to auto-generate a unique grid name automatically? This may be useful in app.config.
> IIS issues example: http://stackoverflow.com/questions/42961879/how-do-i-retrieve-a-started-ignite-instance-when-a-website-restart-occurs-in-iis/42968183#42968183
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)