ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ODE-1033) Assignment of monotonic version numbers in ProcessStore are not thread safe
Date Tue, 18 Aug 2015 12:11:46 GMT

    [ https://issues.apache.org/jira/browse/ODE-1033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701165#comment-14701165
] 

Hudson commented on ODE-1033:
-----------------------------

SUCCESS: Integrated in ODE-trunk-jdk6 #869 (See [https://builds.apache.org/job/ODE-trunk-jdk6/869/])
ODE-1033: incremented version number by holding DB exclusive lock (sathwik: rev 97239d0f557978fecd850cdc01e167460f101bec)
* bpel-store/src/main/java/org/apache/ode/store/ProcessStoreImpl.java
* bpel-store/src/main/java/org/apache/ode/store/jpa/ConfStoreConnectionJpa.java
* bpel-store/src/main/java/org/apache/ode/store/jpa/DbConfStoreConnectionFactory.java
* bpel-store/src/main/java/org/apache/ode/store/hib/ConfStoreConnectionHib.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)

Mime
View raw message