We're updating the issue view to help you get more done. 

Fix distributed locking problem when running in a cluster

Description

This is a hard case to reproduce but using optimistic caches and using a cache only for locks instead of locking the cache to modify is not the best option. Therefore, we need to:

1) review cache types of each cache depending on its usage
2) get rid of optimistic caches since they cannot be locked
3) lock the cache to modify instead of using a cache of locks
4) Fix some NPE in ClusterListener and make it more error-proof

Environment

None

Acceptance Test - Entry

Hard to give a test case here. Generate a hell of a concurrent load on the server, kill nodes, etc. and make sure that presence of contacts in your roster are always correct in all nodes.

Assignee

Gaston Dombiak

Reporter

Gaston Dombiak

Labels

None

Expected Effort

None

Ignite Forum URL

None

Components

Fix versions

Affects versions

Priority

Major
Configure