You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Mateusz Nowakowski (JIRA)" <ji...@apache.org> on 2009/08/19 18:43:14 UTC
[jira] Created: (ODE-652) When ODE gets an runtime exception it
doesn't handle it properly
When ODE gets an runtime exception it doesn't handle it properly
----------------------------------------------------------------
Key: ODE-652
URL: https://issues.apache.org/jira/browse/ODE-652
Project: ODE
Issue Type: Bug
Components: BPEL Runtime, JBI Integration
Affects Versions: 1.3.3
Environment: WinXP, Fuse-3.4.0.4,Apache ODE 1.3.3 JBI
Reporter: Mateusz Nowakowski
When NullPointer was thrown from WHILE.checkCondition() (JIRA ODE-651)
it is only logged and isn't handled at all.
This extension is configured
<ext:faultOnFailure>true</ext:faultOnFailure>
but this NullPointer is not considered as failure and BPEL script simply hangs....
It doesn't return to JBI at all as well as an MessageExchange ERROR or fault.
What is more, this is written to logs a bit later:
2009-08-19 17:01:19,525 [pool-5-thread-48] WARN org.apache.ode.bpel.memdao.ProcessDaoImpl - Discarding in-memory instance 3 because it exceeded its time-to-live: mem.instance(type={https://webservices.sabre.com/websvc}Enhanced_AirBookProcess1.0.1 iid=3)
PS. What is time-to-live for BPEL processes? Is it configurable?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (ODE-652) When ODE gets an runtime exception it
doesn't handle it properly
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745201#action_12745201 ]
Alex Boisvert commented on ODE-652:
-----------------------------------
This behavior is "as designed". Java exceptions occuring inside the engine are never visible to processes.
The time-to-live was discussed here:
http://ode.markmail.org/search/?q=inmem.ttl#query:inmem.ttl+page:1+mid:7ldgsgjuprk7itvl+state:results)
I'll add a mention of it in the documentation.
> When ODE gets an runtime exception it doesn't handle it properly
> ----------------------------------------------------------------
>
> Key: ODE-652
> URL: https://issues.apache.org/jira/browse/ODE-652
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime, JBI Integration
> Affects Versions: 1.3.3
> Environment: WinXP, Fuse-3.4.0.4,Apache ODE 1.3.3 JBI
> Reporter: Mateusz Nowakowski
> Fix For: 1.3.4
>
>
> When NullPointer was thrown from WHILE.checkCondition() (JIRA ODE-651)
> it is only logged and isn't handled at all.
> This extension is configured
> <ext:faultOnFailure>true</ext:faultOnFailure>
> but this NullPointer is not considered as failure and BPEL script simply hangs....
> It doesn't return to JBI at all as well as an MessageExchange ERROR or fault.
> What is more, this is written to logs a bit later:
> 2009-08-19 17:01:19,525 [pool-5-thread-48] WARN org.apache.ode.bpel.memdao.ProcessDaoImpl - Discarding in-memory instance 3 because it exceeded its time-to-live: mem.instance(type={https://webservices.sabre.com/websvc}Enhanced_AirBookProcess1.0.1 iid=3)
> PS. What is time-to-live for BPEL processes? Is it configurable?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-652) When ODE gets an runtime exception it
doesn't handle it properly
Posted by "Mateusz Nowakowski (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mateusz Nowakowski updated ODE-652:
-----------------------------------
Fix Version/s: 1.3.4
> When ODE gets an runtime exception it doesn't handle it properly
> ----------------------------------------------------------------
>
> Key: ODE-652
> URL: https://issues.apache.org/jira/browse/ODE-652
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime, JBI Integration
> Affects Versions: 1.3.3
> Environment: WinXP, Fuse-3.4.0.4,Apache ODE 1.3.3 JBI
> Reporter: Mateusz Nowakowski
> Fix For: 1.3.4
>
>
> When NullPointer was thrown from WHILE.checkCondition() (JIRA ODE-651)
> it is only logged and isn't handled at all.
> This extension is configured
> <ext:faultOnFailure>true</ext:faultOnFailure>
> but this NullPointer is not considered as failure and BPEL script simply hangs....
> It doesn't return to JBI at all as well as an MessageExchange ERROR or fault.
> What is more, this is written to logs a bit later:
> 2009-08-19 17:01:19,525 [pool-5-thread-48] WARN org.apache.ode.bpel.memdao.ProcessDaoImpl - Discarding in-memory instance 3 because it exceeded its time-to-live: mem.instance(type={https://webservices.sabre.com/websvc}Enhanced_AirBookProcess1.0.1 iid=3)
> PS. What is time-to-live for BPEL processes? Is it configurable?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (ODE-652) When ODE gets an runtime exception it
doesn't handle it properly
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert resolved ODE-652.
-------------------------------
Resolution: Invalid
> When ODE gets an runtime exception it doesn't handle it properly
> ----------------------------------------------------------------
>
> Key: ODE-652
> URL: https://issues.apache.org/jira/browse/ODE-652
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime, JBI Integration
> Affects Versions: 1.3.3
> Environment: WinXP, Fuse-3.4.0.4,Apache ODE 1.3.3 JBI
> Reporter: Mateusz Nowakowski
> Fix For: 1.3.4
>
>
> When NullPointer was thrown from WHILE.checkCondition() (JIRA ODE-651)
> it is only logged and isn't handled at all.
> This extension is configured
> <ext:faultOnFailure>true</ext:faultOnFailure>
> but this NullPointer is not considered as failure and BPEL script simply hangs....
> It doesn't return to JBI at all as well as an MessageExchange ERROR or fault.
> What is more, this is written to logs a bit later:
> 2009-08-19 17:01:19,525 [pool-5-thread-48] WARN org.apache.ode.bpel.memdao.ProcessDaoImpl - Discarding in-memory instance 3 because it exceeded its time-to-live: mem.instance(type={https://webservices.sabre.com/websvc}Enhanced_AirBookProcess1.0.1 iid=3)
> PS. What is time-to-live for BPEL processes? Is it configurable?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.