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 Wed, 24 Feb 2016 14:29:18 GMT

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

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

UNSTABLE: Integrated in ODE-1.x #530 (See [https://builds.apache.org/job/ODE-1.x/530/])
ODE-974: enqueue the message for Active Process even if no instance was (sathwik: [https://github.com/apache/ode/commit/6be91e10a7c01a6f487f5130d24a5de4d8ea4be0])
* bpel-runtime/src/main/java/org/apache/ode/bpel/engine/replayer/ReplayerBpelRuntimeContextImpl.java
* bpel-runtime/src/main/java/org/apache/ode/bpel/engine/replayer/ReplayerContext.java
* bpel-runtime/src/main/java/org/apache/ode/bpel/engine/replayer/Replayer.java
* bpel-runtime/src/main/java/org/apache/ode/bpel/engine/BpelProcess.java
* bpel-runtime/src/main/java/org/apache/ode/bpel/engine/BpelEngineImpl.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