Concurrent access to not synchronized HashMap

Description

We use stripes for a long time but today several threads hung with such stack-trace:

AFAIK, that is how not-synchronized java hash map react to concurrent modification.

Possible solutions include update HashMap to ConcurrentHashMap, use of Collections.synchronizedMap(), put synchronized keyword to BindingPolicyManager.getInstance().

Environment

None

Assignee

Unassigned

Reporter

Andrei

Labels

None

Components

Affects versions

Priority

Critical
Configure