You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2010/04/13 14:29:28 UTC
[jira] Updated: (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:all-tabpanel ]
Tammo van Lessen updated ODE-744:
---------------------------------
Fix Version/s: 1.3.5
> 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
> Fix For: 1.3.5
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira