[
https://issues.apache.org/jira/browse/ODE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701157#comment-14701157
]
Hudson commented on ODE-1033:
-----------------------------
SUCCESS: Integrated in ODE-1.x #515 (See
[https://builds.apache.org/job/ODE-1.x/515/])
ODE-1033: incremented version number by holding DB exclusive lock (sathwik:
https://github.com/apache/ode/commit/9760c4f252e21a539cc44be846d0f6a628d4373a)
*
bpel-store/src/main/java/org/apache/ode/store/jpa/DbConfStoreConnectionFactory.java
* bpel-store/src/main/java/org/apache/ode/store/hib/ConfStoreConnectionHib.java
* bpel-store/src/main/java/org/apache/ode/store/ProcessStoreImpl.java
* bpel-store/src/main/java/org/apache/ode/store/jpa/ConfStoreConnectionJpa.java
> Assignment of monotonic version numbers in ProcessStore are not thread safe
> ---------------------------------------------------------------------------
>
> Key: ODE-1033
> URL: https://issues.apache.org/jira/browse/ODE-1033
> Project: ODE
> Issue Type: Bug
> Components: Deployment
> Affects Versions: 1.3.6
> Reporter: Sathwik Bantwal Premakumar
> Assignee: Sathwik Bantwal Premakumar
> Fix For: 1.3.7, 1.4
>
>
> While load testing, came across this issue where some of the deployment units
> get the same version numbers and the deployment fails.
> During concurrent deployments, the code block where the version number is
> retrieved and set on the deployment unit in deploy operation of
> ProcessStoreImpl results in returning same version numbers for multiple
> threads.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
