ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christoph M. Pflügler (JIRA) <j...@apache.org>
Subject [jira] Commented: (ODE-263) onAlarm is trigered only after completed activity
Date Tue, 10 Jun 2008 17:41:45 GMT

    [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12603944#action_12603944

Christoph M. Pflügler commented on ODE-263:


as I need this feature for my thesis, I tested it with Axis2.

The relevant BPEL part:
<scope name="timeout">
					<throw faultName="TimeoutFault"/>
		<receive partnerLink="testing" portType="testWsdl:testingPT" operation="testIt" variable="DataTOin"
		<invoke partnerLink="ws1" portType="testWsdl:ws1PT" operation="doIt" inputVariable="DataTOin"
		<reply partnerLink="testing" portType="testWsdl:testingPT" operation="testIt" variable="DataTOout">

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.


> 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
>            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.

View raw message