There are a number of different thread pools used by the SOA Suite runtime. Some of them are used to run background tasks such as keeping track of which processes need to be woken after a BPEL
wait activity or waiting for messages to arrive. Other threads are used to execute composites. In this section, we will focus on threads as
they apply to the execution of our composite application. The SOA infrastructure obtains its threads from the underlying applications server but manages those threads itself.
Messages arrive in two distinct interaction patterns. They are either one-way messages, which are not part of an operation requiring a reply, or they are synchronous request/reply messages with a response ...