You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Matthieu Riou (JIRA)" <ji...@apache.org> on 2006/10/04 00:05:21 UTC
[jira] Created: (ODE-59) Runtime exceptions should bubble up
Runtime exceptions should bubble up
-----------------------------------
Key: ODE-59
URL: http://issues.apache.org/jira/browse/ODE-59
Project: Apache Ode
Issue Type: Bug
Components: BPEL Runtime
Affects Versions: Incubator
Reporter: Matthieu Riou
Fix For: Incubator
Curremtly in the ASSIGN there's the following code:
try {
copy(aCopy);
} catch (FaultException fault) {
faultData = createFault(fault.getQName(), aCopy, fault
.getMessage());
break;
} catch (Exception ex) {
__log.fatal("Unexpected exception in assignment, terminating process", ex);
instance(ASSIGN.this);
getBpelRuntimeContext().terminate();
break;
}
Which practically means that any non-fault exception will result in the process terminating. However an engine failure (a sneaky NPE hidden in a rarely executed piece of code) shouldn't affect the process. So such an exception should bubble up to the IL and trigger a transaction rollback.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (ODE-59) Runtime exceptions should bubble up
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/ODE-59?page=all ]
Matthieu Riou resolved ODE-59.
------------------------------
Resolution: Won't Fix
Assignee: Matthieu Riou
Actually they shouldn't. Process recovery takes care of that.
> Runtime exceptions should bubble up
> -----------------------------------
>
> Key: ODE-59
> URL: http://issues.apache.org/jira/browse/ODE-59
> Project: Apache Ode
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: Incubator
> Reporter: Matthieu Riou
> Assigned To: Matthieu Riou
> Fix For: Incubator
>
>
> Curremtly in the ASSIGN there's the following code:
> try {
> copy(aCopy);
> } catch (FaultException fault) {
> faultData = createFault(fault.getQName(), aCopy, fault
> .getMessage());
> break;
> } catch (Exception ex) {
> __log.fatal("Unexpected exception in assignment, terminating process", ex);
> instance(ASSIGN.this);
> getBpelRuntimeContext().terminate();
> break;
> }
> Which practically means that any non-fault exception will result in the process terminating. However an engine failure (a sneaky NPE hidden in a rarely executed piece of code) shouldn't affect the process. So such an exception should bubble up to the IL and trigger a transaction rollback.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (ODE-59) Runtime exceptions should bubble up
Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthieu Riou closed ODE-59.
----------------------------
> Runtime exceptions should bubble up
> -----------------------------------
>
> Key: ODE-59
> URL: https://issues.apache.org/jira/browse/ODE-59
> Project: Ode
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: Incubator
> Reporter: Matthieu Riou
> Assignee: Matthieu Riou
> Fix For: Incubator
>
>
> Curremtly in the ASSIGN there's the following code:
> try {
> copy(aCopy);
> } catch (FaultException fault) {
> faultData = createFault(fault.getQName(), aCopy, fault
> .getMessage());
> break;
> } catch (Exception ex) {
> __log.fatal("Unexpected exception in assignment, terminating process", ex);
> instance(ASSIGN.this);
> getBpelRuntimeContext().terminate();
> break;
> }
> Which practically means that any non-fault exception will result in the process terminating. However an engine failure (a sneaky NPE hidden in a rarely executed piece of code) shouldn't affect the process. So such an exception should bubble up to the IL and trigger a transaction rollback.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.