[
https://issues.apache.org/jira/browse/ODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845311#action_12845311
]
Rafal Rusin commented on ODE-744:
---------------------------------
I believe this problem comes from:
java.lang.NullPointerException
at java.io.ByteArrayInputStream.<init>(ByteArrayInputStream.java:89)
at
org.apache.ode.bpel.engine.migration.OutstandingRequestsMigration.migrate(OutstandingRequestsMigration.java:57)
at
org.apache.ode.bpel.engine.migration.MigrationHandler$2.call(MigrationHandler.java:87)
at
org.apache.ode.bpel.engine.migration.MigrationHandler$2.call(MigrationHandler.java:77)
at
org.apache.ode.scheduler.simple.SimpleScheduler.execTransaction(SimpleScheduler.java:274)
at
org.apache.ode.bpel.engine.migration.MigrationHandler.migrate(MigrationHandler.java:76)
at
org.apache.ode.bpel.engine.BpelServerImpl.start(BpelServerImpl.java:159)
at org.apache.ode.axis2.ODEServer.init(ODEServer.java:187)
at org.apache.ode.axis2.ODEServer.init(ODEServer.java:127)
at
org.apache.ode.axis2.hooks.ODEAxisServlet.init(ODEAxisServlet.java:53)
which occurs when doing migration for completed instance (execution state is
then null). This yields to rollbacking whole migration. I'll prepare a fix for
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.
