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-974) On process versioning, instances of retired version are not picking the data from BPEL_UNMATCHED
Date Tue, 05 Apr 2016 08:20:25 GMT

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

Hudson commented on ODE-974:
----------------------------

SUCCESS: Integrated in ODE-1.x #533 (See [https://builds.apache.org/job/ODE-1.x/533/])
ODE-974: Sort the processes so that the active one comes last, changed (sathwik: [https://github.com/apache/ode/commit/51d58ddd70dca2fdd7c28d757780134085964ac2])
* bpel-runtime/src/main/java/org/apache/ode/bpel/engine/BpelProcess.java
* bpel-runtime/src/main/java/org/apache/ode/bpel/engine/BpelEngineImpl.java
* dao-hibernate/src/main/java/org/apache/ode/daohib/bpel/hobj/HCorrelationSet.java
* bpel-dao/src/main/java/org/apache/ode/bpel/dao/ProcessDAO.java
* dao-jpa/src/main/java/org/apache/ode/dao/jpa/ProcessDAOImpl.java
* dao-hibernate/src/main/java/org/apache/ode/daohib/bpel/ProcessDaoImpl.java


> On process versioning, instances of retired version are not picking the data from BPEL_UNMATCHED
> ------------------------------------------------------------------------------------------------
>
>                 Key: ODE-974
>                 URL: https://issues.apache.org/jira/browse/ODE-974
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>            Reporter: Jayant Vaish
>            Assignee: Sathwik Bantwal Premakumar
>            Priority: Critical
>             Fix For: 1.3.7, 1.4
>
>         Attachments: ODE_974.zip, sample10534.zip
>
>
> If there is a process which receives the data from another process in such a manner that
the data arrives first and then the instance reaches the activity which needs it, the instance
picks the data from the BPEL_UNMATCHED table.
> If we deploy the process again, then the running instances of retired process are not
picking data from BPEL_UNMATCHED hence not getting completed.
> I have attached the process. Here are the steps to reproduce :
> 1. Deploy the process. Start the parent process from console.
> 2. Deploy again.
> 3. After one min you will see that the child process has completed, and there is an entry
in BPEL_UNMATCHED.
> 4. After two mins you will see that parent process is still waiting for the message from
child process, which has already came and currently is in BPEL_UNMATCHED table.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message