[
https://issues.apache.org/jira/browse/ODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12799305#action_12799305
]
Karthick Sankarachary commented on ODE-744:
-------------------------------------------
This may be a false alarm. I took a quick look at the migration handler and it
seems like it's doing what it's supposed to do.
> 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.
