ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Karachentsev (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (IGNITE-4667) Throw exception on starting client cache when indexed types cannot be loaded
Date Tue, 14 Mar 2017 07:59:41 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-4667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitry Karachentsev reassigned IGNITE-4667:
-------------------------------------------

    Assignee: Dmitry Karachentsev

> 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
>
> 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)

Mime
View raw message