[
https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624030#action_12624030
]
Matthieu Riou commented on ODE-263:
-----------------------------------
Does it fix the issue for you? I'm actually a bit surprised by the patch, I was
thinking this was probably a problem with the JBI IL blocking the engine thread
during invocation, which wouldn't allow the process to execute during that
time. Are you using the sync or async JBI consumer?
> onAlarm is trigered only after completed activity
> -------------------------------------------------
>
> Key: ODE-263
> URL: https://issues.apache.org/jira/browse/ODE-263
> Project: ODE
> Issue Type: Bug
> Components: BPEL Runtime
> Affects Versions: 1.1.1
> Environment: FUSE ESB 3.3.0.2
> Reporter: Mateusz Nowakowski
> Fix For: 1.3
>
> Attachments: throw-invoke.diff
>
>
> Let say I have very short onAlarm eventHandler:
> <bpel:eventHandlers>
> <bpel:onAlarm
> <bpel:for"PT5S"</bpel:for>
> <bpel:scope>
> <bpel:throw
> faultName="tns:TimeoutFault"/>
> </bpel:scope>
>
> </bpel:onAlarm>
> </bpel:eventHandlers>
> and process contains very long activity (invoke, flow etc.).
> Alarm is triggered only after very long activity completes, not after
> specified amount of time.
> I tested it using invoke activity which invokes very long external web
> service.
> ODE is launched using default async mode.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
