[ODE-577] No separate threads for ExternalServices replies

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.2
• Assignee: Alexis Midon
• Reporter: Alexis Midon
• Created: 09/Apr/09 22:03
• Updated: 24/Apr/09 00:54
• Resolved: 15/Apr/09 01:50

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.

Issue Links

• is related to: ODE-533 Share a connection manager across SoapExternalServices