You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/03 07:50:04 UTC

[jira] [Commented] (IGNITE-4667) Throw exception on starting client cache when indexed types cannot be loaded

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

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

Github user dkarachentsev closed the pull request at:

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


> Throw exception on starting client cache when indexed types cannot be loaded
> ----------------------------------------------------------------------------
>
>                 Key: IGNITE-4667
>                 URL: https://issues.apache.org/jira/browse/IGNITE-4667
>             Project: Ignite
>          Issue Type: Bug
>          Components: cache
>    Affects Versions: 1.8
>            Reporter: Dmitry Karachentsev
>            Assignee: Dmitry Karachentsev
>             Fix For: 2.1
>
>
> Assume following situation:
> 1. Server node configured cache indexed types with classes that client node doesn't have.
> 2. Start server.
> 3. Start client. Client successfully connected.
> 4. Try to get cache on client node.
> 5. Was thrown exception in GridQueryProcessor and request for cache on client node hangs forever.
> If on some reason cache couldn't be initialized, exception must be thrown on Ignite.cache() operation.



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