You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Christoph M. Pflügler (JIRA)" <ji...@apache.org> on 2008/06/12 21:14:47 UTC
[jira] Issue Comment Edited: (ODE-263) onAlarm is trigered only
after completed activity
[ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603944#action_12603944 ]
flocke edited comment on ODE-263 at 6/12/08 12:13 PM:
---------------------------------------------------------------------
Hi,
as I need this feature for my thesis, I tested it with Axis2.
The relevant BPEL part:
<scope name="timeout">
<eventHandlers>
<onAlarm>
<for>'PT7S'</for>
<scope>
<sequence>
<throw faultName="TimeoutFault"/>
</sequence>
</scope>
</onAlarm>
</eventHandlers>
<sequence>
<receive partnerLink="testing" portType="testWsdl:testingPT" operation="testIt" variable="DataTOin" createInstance="yes">
</receive>
<invoke partnerLink="ws1" portType="testWsdl:ws1PT" operation="doIt" inputVariable="DataTOin" outputVariable="DataTOout">
</invoke>
<reply partnerLink="testing" portType="testWsdl:testingPT" operation="testIt" variable="DataTOout">
</reply>
</sequence>
</scope>
partnerLink ws1 would reply after 50 seconds, I get the TimeoutFault message as reply from the process after around 30 seconds after AxisFault: Read timed out.. So looks like it doesn't work with an Axis2 based deployment either.
HTH,
Christoph
was (Author: flocke):
Hi,
as I need this feature for my thesis, I tested it with Axis2.
The relevant BPEL part:
<scope name="timeout">
<eventHandlers>
<onAlarm>
<for>'PT7S'</for>
<scope>
<sequence>
<throw faultName="TimeoutFault"/>
</sequence>
</scope>
</onAlarm>
</eventHandlers>
<sequence>
<receive partnerLink="testing" portType="testWsdl:testingPT" operation="testIt" variable="DataTOin" createInstance="yes">
</receive>
<invoke partnerLink="ws1" portType="testWsdl:ws1PT" operation="doIt" inputVariable="DataTOin" outputVariable="DataTOout">
</invoke>
<reply partnerLink="testing" portType="testWsdl:testingPT" operation="testIt" variable="DataTOout">
</reply>
</sequence>
</scope>
partnerLink ws1 would reply after 50 seconds, however I get the TimeoutFault message as reply from the process after the 7 seconds. So looks like it works with an Axis2 based deployment.
HTH,
Christoph
> 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.2
>
>
> 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.