You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Sean Ahn (JIRA)" <ji...@apache.org> on 2010/01/12 02:22:54 UTC
[jira] Created: (ODE-744) Long running instances fail due to the
changes in the soup contract -
Long running instances fail due to the changes in the soup contract -
----------------------------------------------------------------------
Key: ODE-744
URL: https://issues.apache.org/jira/browse/ODE-744
Project: ODE
Issue Type: Bug
Components: BPEL Runtime
Reporter: Sean Ahn
Assignee: Sean Ahn
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.
[jira] Commented: (ODE-744) soup cannot be restored due to the
OustandingRequestManager to IMAManager change
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845342#action_12845342 ]
Hudson commented on ODE-744:
----------------------------
Integrated in ODE-1.x #79 (See [http://hudson.zones.apache.org/hudson/job/ODE-1.x/79/])
: NPE fix for OutstandingRequestsMigration
> 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.
[jira] Commented: (ODE-744) soup cannot be restored due to the
OustandingRequestManager to IMAManager change
Posted by "Karthick Sankarachary (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (ODE-744) soup cannot be restored due to the
OustandingRequestManager to IMAManager change
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (ODE-744) soup cannot be restored due to the
OustandingRequestManager to IMAManager change
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn reassigned ODE-744:
----------------------------
Assignee: Karthick Sankarachary (was: Sean Ahn)
> 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.
[jira] Commented: (ODE-744) soup cannot be restored due to the
OustandingRequestManager to IMAManager change
Posted by "Rafal Rusin (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (ODE-744) soup cannot be restored due to the
OustandingRequestManager to IMAManager change
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen resolved ODE-744.
----------------------------------
Resolution: Fixed
Assignee: Rafal Rusin (was: Karthick Sankarachary)
This has been fixed for a while, so we can close this issue.
> 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: Rafal Rusin
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-744) soup cannot be restored due to the
OustandingRequestManager to IMAManager change
Posted by "Sean Ahn (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sean Ahn updated ODE-744:
-------------------------
Summary: soup cannot be restored due to the OustandingRequestManager to IMAManager change (was: Long running instances fail due to the changes in the soup contract - )
> 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: Sean Ahn
>
> 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.
[jira] Commented: (ODE-744) soup cannot be restored due to the
OustandingRequestManager to IMAManager change
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845685#action_12845685 ]
Hudson commented on ODE-744:
----------------------------
Integrated in ODE-1.x #80 (See [http://hudson.zones.apache.org/hudson/job/ODE-1.x/80/])
: Improved logging
> 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.
[jira] Updated: (ODE-744) soup cannot be restored due to the
OustandingRequestManager to IMAManager change
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ 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