ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Fonden" <christian.fon...@die-rooter.de>
Subject Asynch Extension Activity does not complete properly
Date Sat, 16 May 2009 15:58:57 GMT
Hello Oders,

I think i just found a bug in the ODE trunk in ExtensionContext. The 
scenario is
- An extension Activity extending AbstractAsynchExtensionOperation
- the run method does neither complete with errors nor it completes 
successfully (intended!)
- a java timer waits 10 seconds and the calls context.completeWithFault.
- then the activity gets marked as faulted, but the process runs until it is 
stopped by the 30 second axis2 call timeout.

I think the situation that the activity gets marked as faulted is somehow 
not propagated to the navigator, as the process could be completed just 
after the timer fires (e.g. after 10 seconds, as shown above).

Does this seem plausible? If someone is interested i can supply the 
extension code and the according bpel file.


View raw message