[jira] Updated: (ODE-263) onAlarm is trigered only after completed activity

["Pawel Stawicki (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Pawel Stawicki updated ODE-263:
-------------------------------

    Attachment: throw-invoke.diff

I've made a patch for this bug.
I'm not sure whether it is correct, if someone could look at it. 

The patch is based on the org.apache.ode.bpel.runtime.WAIT class.



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