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

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

GitHub user voipp opened a pull request:

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

    IGNITE-1094 Ignite.createCache(CacheConfiguration) hangs if some exception 
occurs during cache initialization

    

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

    $ git pull https://github.com/voipp/ignite ignite-1094

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

    https://github.com/apache/ignite/pull/1581.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 #1581
    
----
commit d5dfb98af424db47bc67919c6d332ff335477f08
Author: sevdokimov <sergey.evdoki...@jetbrains.com>
Date:   2015-07-04T14:38:36Z

    # IGNITE-1094 Add test.

commit ef77a55874dad3b5f99134f0d1e6e4901ac424c1
Author: voipp <aleksa...@gmail.com>
Date:   2017-02-28T09:45:47Z

    IGNITE-1094 handling cache start exception

----


> Ignite.createCache(CacheConfiguration) hangs if some exception occurs during 
> cache initialization
> -------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-1094
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1094
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: sprint-7
>            Reporter: Sergey Evdokimov
>            Assignee: Alexey Kuznetsov
>              Labels: Muted_test
>
> User can pass broken configuration, for example, store factory that throws 
> exception from create() method. I created test to demonstrate the problem. 
> See IgniteDynamicCacheStartSelfTest#testBrokenStoreFactory in 'ignite-1094' 
> branch 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to