[ 
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...@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.

Reply via email to