You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Rafal Rusin (JIRA)" <ji...@apache.org> on 2010/01/12 10:38:54 UTC

[jira] Commented: (ODE-744) soup cannot be restored due to the OustandingRequestManager to IMAManager change

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

Rafal Rusin commented on ODE-744:
---------------------------------

That's weird. I have implemented migration here: bpel-runtime/src/main/java/org/apache/ode/bpel/engine/migration/OutstandingRequestsMigration.java.
I have tested it manually and it worked. Maybe there's some problem within it. 

> soup cannot be restored due to the OustandingRequestManager to IMAManager change
> --------------------------------------------------------------------------------
>
>                 Key: ODE-744
>                 URL: https://issues.apache.org/jira/browse/ODE-744
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>            Reporter: Sean Ahn
>            Assignee: Karthick Sankarachary
>
> The _outstandingRequests that's part of the soup has been changed to IMAManager type, with ODE-634: "Event Handlers not working fix". Due to the change, when you have a long running process, and when you get the new ODE build, the instance cannot be restored from the soup anymore.
> In the ExecutionQueueImpl.read(InputStream) method, check the type from the soup,
> 1. If the existing type is IMAManager, the code is fine.
> 2. If the existing type is the OutstandingRequestManager, create a new IMAManager from the OutstandingRequestManager.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.