Ran Ziv created ARIA-79:
---------------------------
Summary: Handle concurrency issues when running multiple operations
Key: ARIA-79
URL: https://issues.apache.org/jira/browse/ARIA-79
Project: AriaTosca
Issue Type: Bug
Reporter: Ran Ziv
It seems like currently, the scope of the storage session is too large, meaning
that when one operation commits changes to the storage (e.g. updating a task's
state) then runtime properties that are being modified by another will get
committed too.
Need to look into how to isolate / lock / separate these sessions (possibly via
subtransactions?)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
