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

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.8
• Fix Version/s: 2.1
• Component/s: cache
• Assignee: Dmitry Karachentsev
• Reporter: Dmitry Karachentsev
• Created: 08/Feb/17 07:57
• Updated: 03/Jun/17 07:49
• Resolved: 10/Apr/17 07:55

Description

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.

Issue Links

• links to: GitHub Pull Request #2012