ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Tupitsyn (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-4856) .NET: StopAll on AppDomain unload
Date Wed, 05 Apr 2017 08:06:41 GMT

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

Pavel Tupitsyn commented on IGNITE-4856:

* {{Ignition.StopAll}} on domain unload implemented
* {{IgniteConfiguration.AutoGenerateIgniteInstanceName}} added

Checked with IIS & ASP.NET, user has to specify {{AutoGenerateIgniteInstanceName}} in
config and can work without any issues after that.

[~vozerov] please have a look.

> .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
>            Assignee: 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

View raw message