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

Memory store may not register iteration in some circumstances

Description

It is possible to completely lock up a thread if a stack overflow occurs during the lock acquisition phase of a read. This is potentially related to SES-1008, but may be an extension of the issue. I've attached a simple test case which locks up 100% of the time for me. The creation of the stack in the test is synthetic, but if you happen to go in to a read call with a stack of just the wrong depth...

Environment

None

Status

Assignee

JeenB

Reporter

Nick Giles

Labels

None

Components

Fix versions

Affects versions

2.7.3

Priority

Major