You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Mateusz Nowakowski (JIRA)" <ji...@apache.org> on 2008/04/08 10:49:28 UTC

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

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


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.


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

Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624041#action_12624041 ] 

Matthieu Riou commented on ODE-263:
-----------------------------------

Okay, the patch looks good and the termination listener was missing anyway. I'll just add some logging because in this case, we're ignoring the response (or fault) entirely, which could be surprising in some cases (people don't always intend to do what they do).

Thanks for looking into this an providing a patch!

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


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

Posted by "Pawel Stawicki (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623322#action_12623322 ] 

Pawel Stawicki commented on ODE-263:
------------------------------------

I have the same bug in a <flow>

the flow looks like this:

<flow>
    <invoke ...>
    <sequence> 
        <wait> 
            <for>'PT1S'<for>
        </wait>
        <throw ...>
    </sequence>
</flow>


the "throw" don't interrupt the "invoke" statement.



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


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

Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthieu Riou resolved ODE-263.
-------------------------------

    Resolution: Fixed
      Assignee: Matthieu Riou

Patch applied with minor logging additions.

> 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
>            Assignee: Matthieu Riou
>             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.


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

Posted by "Mateusz Nowakowski (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589603#action_12589603 ] 

Mateusz Nowakowski commented on ODE-263:
----------------------------------------

Any comment ?

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


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

Posted by "Pawel Stawicki (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624035#action_12624035 ] 

Pawel Stawicki commented on ODE-263:
------------------------------------

Yes it fix my issue.

I'm only not sure whether the termination of "invokeResponseChannel" is well done.

> Are you using the sync or async JBI consumer?
I'm using 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.


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

Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
    [ 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.


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

Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623356#action_12623356 ] 

Matthieu Riou commented on ODE-263:
-----------------------------------

Is that using the JBI integration layer as well? Normally it should work using the Axis2 IL (invocation doesn't "block" the engine).

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


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

Posted by "Mateusz Nowakowski (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mateusz Nowakowski updated ODE-263:
-----------------------------------

    Fix Version/s: 1.2

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


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

Posted by "Pawel Stawicki (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12623371#action_12623371 ] 

Pawel Stawicki commented on ODE-263:
------------------------------------

I'm using  ServiceMix.

It doesn't seem to "block" the engine,
(I can see the throw in my logs)

It only doesn't cancel the "invoke".



when I use "receive" instead  of "invoke":

<flow>
    <receive ...>
    <sequence>
        <wait>
            <for>'PT1S'<for>
        </wait>
        <throw ...>
    </sequence>
</flow> 

everything works fine.
  

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


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

Posted by "Mateusz Nowakowski (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590367#action_12590367 ] 

Mateusz Nowakowski commented on ODE-263:
----------------------------------------

We are using only FUSE+ODE environment. 
I'll try to reproduce with an Axis2, but I don't know when I'll find time to do that :)

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


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

Posted by "Christoph M. Pflügler (JIRA)" <ji...@apache.org>.
    [ 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:
-------------------------------------------

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.


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

Posted by "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.


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

Posted by "Matthieu Riou (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589689#action_12589689 ] 

Matthieu Riou commented on ODE-263:
-----------------------------------

I haven't had a chance to look at it yet, although I'm pretty sure it only happens when deployed in ServiceMix. Have you witnessed the same behavior 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 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.


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

Posted by "Christoph M. Pflügler (JIRA)" <ji...@apache.org>.
    [ 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.