You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2008/12/17 23:08:44 UTC
[jira] Created: (ODE-467) Synchronous BPEL with asynchronous
transport may time out
Synchronous BPEL with asynchronous transport may time out
---------------------------------------------------------
Key: ODE-467
URL: https://issues.apache.org/jira/browse/ODE-467
Project: ODE
Issue Type: Bug
Components: Axis2 Integration
Affects Versions: 2.0
Reporter: Tammo van Lessen
As described in this thread: http://ode.markmail.org/search/?q=#query:+page:1+mid:suowpi2x6qdd3qre+state:results
ODE can be used with Axis' addressing module to use the ws-addr-wsdl binding. The header processing works basically fine, however a long running process will result in a time out.
I assume this is because the invocation is not decoupled and is therefore blocking for in-out MEPs (in OdeService.invokeOde(...))
Any suggestions? Does this also apply to JMS/SMTP/.../async transports?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (ODE-467) Synchronous BPEL with asynchronous
transport may time out
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated ODE-467:
---------------------------------
Fix Version/s: 2.0-beta3
(was: 1.3.5)
> Synchronous BPEL with asynchronous transport may time out
> ---------------------------------------------------------
>
> Key: ODE-467
> URL: https://issues.apache.org/jira/browse/ODE-467
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Affects Versions: 2.0
> Reporter: Tammo van Lessen
> Fix For: 2.0-beta3
>
>
> As described in this thread: http://ode.markmail.org/search/?q=#query:+page:1+mid:suowpi2x6qdd3qre+state:results
> ODE can be used with Axis' addressing module to use the ws-addr-wsdl binding. The header processing works basically fine, however a long running process will result in a time out.
> I assume this is because the invocation is not decoupled and is therefore blocking for in-out MEPs (in OdeService.invokeOde(...))
> Any suggestions? Does this also apply to JMS/SMTP/.../async transports?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ODE-467) Synchronous BPEL with asynchronous
transport may time out
Posted by "Tammo van Lessen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ODE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tammo van Lessen updated ODE-467:
---------------------------------
Fix Version/s: 1.3.5
> Synchronous BPEL with asynchronous transport may time out
> ---------------------------------------------------------
>
> Key: ODE-467
> URL: https://issues.apache.org/jira/browse/ODE-467
> Project: ODE
> Issue Type: Bug
> Components: Axis2 Integration
> Affects Versions: 2.0
> Reporter: Tammo van Lessen
> Fix For: 1.3.5
>
>
> As described in this thread: http://ode.markmail.org/search/?q=#query:+page:1+mid:suowpi2x6qdd3qre+state:results
> ODE can be used with Axis' addressing module to use the ws-addr-wsdl binding. The header processing works basically fine, however a long running process will result in a time out.
> I assume this is because the invocation is not decoupled and is therefore blocking for in-out MEPs (in OdeService.invokeOde(...))
> Any suggestions? Does this also apply to JMS/SMTP/.../async transports?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira