You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alexis Midon (JIRA)" <ji...@apache.org> on 2009/04/10 00:05:13 UTC

[jira] Created: (ODE-577) No separate threads for ExternalServices replies

No separate threads for ExternalServices replies
------------------------------------------------

                 Key: ODE-577
                 URL: https://issues.apache.org/jira/browse/ODE-577
             Project: ODE
          Issue Type: Improvement
            Reporter: Alexis Midon
            Assignee: Alexis Midon
             Fix For: 1.3.1, 2.0



SoapExternalService and HttpExternalService invoke services in a separate thread started in the afterCompletion phase of the initial transaction. Answers of these invocations are also processed in a new transaction, in another thread.   See org.apache.ode.axis2.SoapExternalService#reply for an illustration.

Obviously the transaction is mandatory, but it does have to happen in another thread.
So the improvement would be to replace the call to org.apache.ode.bpel.iapi.Scheduler#execIsolatedTransaction with org.apache.ode.bpel.iapi.Scheduler#execTransaction.





-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Work started: (ODE-577) No separate threads for ExternalServices replies

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

Work on ODE-577 started by Alexis Midon.

> No separate threads for ExternalServices replies
> ------------------------------------------------
>
>                 Key: ODE-577
>                 URL: https://issues.apache.org/jira/browse/ODE-577
>             Project: ODE
>          Issue Type: Improvement
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>             Fix For: 1.3.1, 2.0
>
>
> SoapExternalService and HttpExternalService invoke services in a separate thread started in the afterCompletion phase of the initial transaction. Answers of these invocations are also processed in a new transaction, in another thread.   See org.apache.ode.axis2.SoapExternalService#reply for an illustration.
> Obviously the transaction is mandatory, but it does not have to happen in another thread.
> So the improvement would be to replace the call to org.apache.ode.bpel.iapi.Scheduler#execIsolatedTransaction with org.apache.ode.bpel.iapi.Scheduler#execTransaction.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (ODE-577) No separate threads for ExternalServices replies

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

Alexis Midon resolved ODE-577.
------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 2.0)

The issue is not relevant in trunk.

> No separate threads for ExternalServices replies
> ------------------------------------------------
>
>                 Key: ODE-577
>                 URL: https://issues.apache.org/jira/browse/ODE-577
>             Project: ODE
>          Issue Type: Improvement
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>             Fix For: 1.3.1
>
>
> SoapExternalService and HttpExternalService invoke services in a separate thread started in the afterCompletion phase of the initial transaction. Answers of these invocations are also processed in a new transaction, in another thread.   See org.apache.ode.axis2.SoapExternalService#reply for an illustration.
> Obviously the transaction is mandatory, but it does not have to happen in another thread.
> So the improvement would be to replace the call to org.apache.ode.bpel.iapi.Scheduler#execIsolatedTransaction with org.apache.ode.bpel.iapi.Scheduler#execTransaction.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Closed: (ODE-577) No separate threads for ExternalServices replies

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

Alexis Midon closed ODE-577.
----------------------------


on the road to 1.3.1

> No separate threads for ExternalServices replies
> ------------------------------------------------
>
>                 Key: ODE-577
>                 URL: https://issues.apache.org/jira/browse/ODE-577
>             Project: ODE
>          Issue Type: Improvement
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>             Fix For: 1.3.1
>
>
> SoapExternalService and HttpExternalService invoke services in a separate thread started in the afterCompletion phase of the initial transaction. Answers of these invocations are also processed in a new transaction, in another thread.   See org.apache.ode.axis2.SoapExternalService#reply for an illustration.
> Obviously the transaction is mandatory, but it does not have to happen in another thread.
> So the improvement would be to replace the call to org.apache.ode.bpel.iapi.Scheduler#execIsolatedTransaction with org.apache.ode.bpel.iapi.Scheduler#execTransaction.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (ODE-577) No separate threads for ExternalServices replies

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

Alexis Midon updated ODE-577:
-----------------------------

    Description: 

SoapExternalService and HttpExternalService invoke services in a separate thread started in the afterCompletion phase of the initial transaction. Answers of these invocations are also processed in a new transaction, in another thread.   See org.apache.ode.axis2.SoapExternalService#reply for an illustration.

Obviously the transaction is mandatory, but it does not have to happen in another thread.
So the improvement would be to replace the call to org.apache.ode.bpel.iapi.Scheduler#execIsolatedTransaction with org.apache.ode.bpel.iapi.Scheduler#execTransaction.





  was:

SoapExternalService and HttpExternalService invoke services in a separate thread started in the afterCompletion phase of the initial transaction. Answers of these invocations are also processed in a new transaction, in another thread.   See org.apache.ode.axis2.SoapExternalService#reply for an illustration.

Obviously the transaction is mandatory, but it does have to happen in another thread.
So the improvement would be to replace the call to org.apache.ode.bpel.iapi.Scheduler#execIsolatedTransaction with org.apache.ode.bpel.iapi.Scheduler#execTransaction.






> No separate threads for ExternalServices replies
> ------------------------------------------------
>
>                 Key: ODE-577
>                 URL: https://issues.apache.org/jira/browse/ODE-577
>             Project: ODE
>          Issue Type: Improvement
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>             Fix For: 1.3.1, 2.0
>
>
> SoapExternalService and HttpExternalService invoke services in a separate thread started in the afterCompletion phase of the initial transaction. Answers of these invocations are also processed in a new transaction, in another thread.   See org.apache.ode.axis2.SoapExternalService#reply for an illustration.
> Obviously the transaction is mandatory, but it does not have to happen in another thread.
> So the improvement would be to replace the call to org.apache.ode.bpel.iapi.Scheduler#execIsolatedTransaction with org.apache.ode.bpel.iapi.Scheduler#execTransaction.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (ODE-577) No separate threads for ExternalServices replies

Posted by "Alexis Midon (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12699018#action_12699018 ] 

Alexis Midon commented on ODE-577:
----------------------------------

committed in 1.X r765029

> No separate threads for ExternalServices replies
> ------------------------------------------------
>
>                 Key: ODE-577
>                 URL: https://issues.apache.org/jira/browse/ODE-577
>             Project: ODE
>          Issue Type: Improvement
>            Reporter: Alexis Midon
>            Assignee: Alexis Midon
>             Fix For: 1.3.1, 2.0
>
>
> SoapExternalService and HttpExternalService invoke services in a separate thread started in the afterCompletion phase of the initial transaction. Answers of these invocations are also processed in a new transaction, in another thread.   See org.apache.ode.axis2.SoapExternalService#reply for an illustration.
> Obviously the transaction is mandatory, but it does not have to happen in another thread.
> So the improvement would be to replace the call to org.apache.ode.bpel.iapi.Scheduler#execIsolatedTransaction with org.apache.ode.bpel.iapi.Scheduler#execTransaction.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.