You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Anurag Aggarwal (JIRA)" <ji...@apache.org> on 2010/05/21 23:45:19 UTC
[jira] Created: (ODE-829) if process is retired the inflight
instances dont work
if process is retired the inflight instances dont work
------------------------------------------------------
Key: ODE-829
URL: https://issues.apache.org/jira/browse/ODE-829
Project: ODE
Issue Type: Bug
Components: BPEL Runtime
Reporter: Anurag Aggarwal
steps to reproduce
1. deploy version of process with two receives
2. create instance by sending message for first receive, but not complete instance
3. deploy newer version of the process with partnerlink removed/renamed
4. send second message for receive for the instance created in 2
we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-829) if process is retired the inflight
instances dont work
Posted by "David Carver (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12871883#action_12871883 ]
David Carver commented on ODE-829:
----------------------------------
I can verify that the latest patch from Anurag fixes the issue, as long as you apply both patches together. In general it is better to resubmit a combined patch instead of having to apply the patches in sequence.
Dave
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Fix For: 1.3.5
>
> Attachments: patch.829, patch.829.1
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-829) if process is retired the inflight
instances dont work
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin resolved ODE-829.
-----------------------------
Fix Version/s: 1.3.5
Resolution: Fixed
Thanks Anurag! Great work!
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Fix For: 1.3.5
>
> Attachments: patch.829
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-829) if process is retired the inflight
instances dont work
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870448#action_12870448 ]
Hudson commented on ODE-829:
----------------------------
Integrated in ODE-trunk-jdk6 #272 (See [http://hudson.zones.apache.org/hudson/job/ODE-trunk-jdk6/272/])
ODE-829: if process is retired the inflight instances dont work (thanks to Anurag Aggarwal)
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Fix For: 1.3.5
>
> Attachments: patch.829
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-829) if process is retired the inflight
instances dont work
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872250#action_12872250 ]
Rafal Rusin commented on ODE-829:
---------------------------------
Sorry, it worked (http://hudson.zones.apache.org/hudson/job/ODE-trunk-jdk6/275/). It looks like timing issues.
Thanks!
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Fix For: 1.3.5
>
> Attachments: patch.829, patch.829.1
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-829) if process is retired the inflight
instances dont work
Posted by "Anurag Aggarwal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anurag Aggarwal updated ODE-829:
--------------------------------
Attachment: patch.829
test case and possible patch attached
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Attachments: patch.829
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-829) if process is retired the inflight
instances dont work
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872215#action_12872215 ]
Hudson commented on ODE-829:
----------------------------
Integrated in ODE-trunk-jdk6 #275 (See [http://hudson.zones.apache.org/hudson/job/ODE-trunk-jdk6/275/])
ODE-829: if process is retired the inflight instances dont work (2nd fix, thanks to Anurag Aggarwal)
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Fix For: 1.3.5
>
> Attachments: patch.829, patch.829.1
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-829) if process is retired the inflight
instances dont work
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870451#action_12870451 ]
Hudson commented on ODE-829:
----------------------------
Integrated in ODE-trunk #280 (See [http://hudson.zones.apache.org/hudson/job/ODE-trunk/280/])
ODE-829: if process is retired the inflight instances dont work (thanks to Anurag Aggarwal)
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Fix For: 1.3.5
>
> Attachments: patch.829
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (ODE-829) if process is retired the
inflight instances dont work
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870453#action_12870453 ]
Rafal Rusin edited comment on ODE-829 at 5/23/10 4:17 PM:
----------------------------------------------------------
If you could verify why this failed, it would be great:
buildr _1.3.5_ clean test:CommunicationJbiTest
05-23@12:10:48 ERROR (BpelProcess.java:215) - Unable to route message exchange 209, EPR was not specified and the target my-role could not be inferred.
java.lang.Exception
at org.apache.log4j.Logger.forcedLog(Logger.java:214)
at org.apache.log4j.Category.log(Category.java:853)
at org.slf4j.impl.Log4jLoggerAdapter.log(Log4jLoggerAdapter.java:509)
at org.apache.commons.logging.impl.SLF4JLocationAwareLog.error(SLF4JLocationAwareLog.java:162)
at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:215)
at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:284)
at org.apache.ode.bpel.engine.BpelProcess.handleJobDetails(BpelProcess.java:432)
at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:481)
at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:450)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:518)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:513)
at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:284)
at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:239)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:512)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:496)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
http://hudson.zones.apache.org/hudson/job/ODE-trunk/280/testReport/
It looks like it's related to routing.
was (Author: rrusin):
If you could verify why this failed, it would be great:
buildr _1.3.5_ clean test:CommunicationJbiTest
05-23@12:10:48 ERROR (BpelProcess.java:215) - Unable to route message exchange 209, EPR was not specified and the target my-role could not be inferred.
java.lang.Exception
at org.apache.log4j.Logger.forcedLog(Logger.java:214)
at org.apache.log4j.Category.log(Category.java:853)
at org.slf4j.impl.Log4jLoggerAdapter.log(Log4jLoggerAdapter.java:509)
at org.apache.commons.logging.impl.SLF4JLocationAwareLog.error(SLF4JLocationAwareLog.java:162)
at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:215)
at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:284)
at org.apache.ode.bpel.engine.BpelProcess.handleJobDetails(BpelProcess.java:432)
at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:481)
at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:450)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:518)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:513)
at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:284)
at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:239)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:512)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:496)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
http://hudson.zones.apache.org/hudson/job/ODE-trunk/280/testReport/
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Fix For: 1.3.5
>
> Attachments: patch.829
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-829) if process is retired the inflight
instances dont work
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12872243#action_12872243 ]
Rafal Rusin commented on ODE-829:
---------------------------------
There are still test failures:
http://hudson.zones.apache.org/hudson/job/ODE-trunk/283/
It looks like it doesn't recognize failures properly now.
BTW. Before sending patch, please run tests:
buildr _1.3.5_ -e hudson clean test
this will disable axis2-war tests.
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Fix For: 1.3.5
>
> Attachments: patch.829, patch.829.1
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (ODE-829) if process is retired the inflight
instances dont work
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin reopened ODE-829:
-----------------------------
If you could verify why this failed, it would be great:
buildr _1.3.5_ clean test:CommunicationJbiTest
05-23@12:10:48 ERROR (BpelProcess.java:215) - Unable to route message exchange 209, EPR was not specified and the target my-role could not be inferred.
java.lang.Exception
at org.apache.log4j.Logger.forcedLog(Logger.java:214)
at org.apache.log4j.Category.log(Category.java:853)
at org.slf4j.impl.Log4jLoggerAdapter.log(Log4jLoggerAdapter.java:509)
at org.apache.commons.logging.impl.SLF4JLocationAwareLog.error(SLF4JLocationAwareLog.java:162)
at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:215)
at org.apache.ode.bpel.engine.BpelProcess.invokeProcess(BpelProcess.java:284)
at org.apache.ode.bpel.engine.BpelProcess.handleJobDetails(BpelProcess.java:432)
at org.apache.ode.bpel.engine.BpelEngineImpl.onScheduledJob(BpelEngineImpl.java:481)
at org.apache.ode.bpel.engine.BpelServerImpl.onScheduledJob(BpelServerImpl.java:450)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:518)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob$1.call(SimpleScheduler.java:513)
at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:284)
at org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:239)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:512)
at org.apache.ode.scheduler.simple.SimpleScheduler$RunJob.call(SimpleScheduler.java:496)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
http://hudson.zones.apache.org/hudson/job/ODE-trunk/280/testReport/
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Fix For: 1.3.5
>
> Attachments: patch.829
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-829) if process is retired the inflight
instances dont work
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rafal Rusin resolved ODE-829.
-----------------------------
Resolution: Fixed
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Fix For: 1.3.5
>
> Attachments: patch.829, patch.829.1
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-829) if process is retired the inflight
instances dont work
Posted by "Anurag Aggarwal (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anurag Aggarwal updated ODE-829:
--------------------------------
Attachment: patch.829.1
Rafal,
can you please try attached patch.829.1
> if process is retired the inflight instances dont work
> ------------------------------------------------------
>
> Key: ODE-829
> URL: https://issues.apache.org/jira/browse/ODE-829
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Reporter: Anurag Aggarwal
> Fix For: 1.3.5
>
> Attachments: patch.829, patch.829.1
>
>
> steps to reproduce
> 1. deploy version of process with two receives
> 2. create instance by sending message for first receive, but not complete instance
> 3. deploy newer version of the process with partnerlink removed/renamed
> 4. send second message for receive for the instance created in 2
> we get mex timeout because BPELEngine tries to call BPELProcess for only process in step 3 (newer version) and no entry in correlation table is found
> Instead BPELEngine should iterate over both the versions
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.