Threading in 10.1.3.3 SOA Suite

The concept of threading plays a vital role in 10.1.3.3 specially for performance issue ,the same is not applicable in 10.1.3.4 onwards

The most important thing that we have to keep in mind is the following concept

Sum of dspMAxThreads across all the domain should be less than the Receiver Threads

What does it mean?

It mean lets suppose you have three domains at your end

domain1,domain2 and domain3

the property can be found at

SOA_HOME/bpel/domains//config/domain.xml


Maximum active dispatcher threads
100

By default the value is 100.

So you need to check the dspMaxThreads for all the domain

and sum up them.Lets suppose it is 100 for each domain so sum of dsp max threads is

300.

So your receiver thread must be greater than or equal to 300

The receiver Thread can be found at following location

SOA_HOME/j2ee//application-deployments/orabpel/ejb_ob_engine/orion-ejb-jar.xml


ReceiverThreads
40


The default value is 40.It should be set to 300 atleast.

While configuring the threads we should start with some small values of dsp MaxThreads


dspMaxThreads property controls the number of instances created for Process 1....ProcessN for that particular domain.So increasing it will incrase the number of instance getting created in the domain.

however the receiverThreads determines how many active threads are there at a point of time so it makes sense to have this value greater than the sum of dspMaxthreads across all the domain.

One important thing to consider is that when ever we apply a patch

thee SOA_HOME\j2ee\oc4j_soa\application-deployments is saved as

SOA_HOME\j2ee\oc4j_soa\application-deployments.sav

and a new directory with same name as original is created

and so a new orion-ejb-jar.xml is created.

Hence when ever you apply a patch you need to remodify these things in order to work it properly.Most of the time it is the main performance issue so make sure you have tuned the threads properly.

With 10.1.3.4 onwards the threading model has changed so these changes are not required.

Infact in 10.1.3.4 the following properties are not there

dspMinThreads ,dspMaxThreads,dspInvokeAllocFactor

they have been replaced by following properties

dspInvokeThreads and dspEngineThreads

The relation ship now is different

dspInvokeThreads = dspInvokeAllocFactor * dspMaxThreads;

dspEngineThreads = dspMaxThreads - dspInvokeThreads;


From 11g not sure all these concepts have been removed as it is totally on weblogic container.