ignite-issues mailing list archives

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

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

ASF GitHub Bot commented on IGNITE-4856:
----------------------------------------

GitHub user ptupitsyn opened a pull request:

    https://github.com/apache/ignite/pull/1732

    IGNITE-4856 .NET: StopAll on AppDomain unload

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-4856

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/1732.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1732
    
----
commit c3431e901678ea1520bfc647b935e7d425b839d4
Author: Igor Sapego <igorsapg@gmail.com>
Date:   2017-04-04T16:07:49Z

    IGNITE-3583: Replaced passing by value with passing by reference

commit 0ef9046373846b7f79ced81468ff461172c44995
Author: Pavel Tupitsyn <ptupitsyn@apache.org>
Date:   2017-04-05T08:00:20Z

    IGNITE-4856 .NET: StopAll on AppDomain unload

----


> .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
(v6.3.15#6346)

Mime
View raw message