Resolution:
Description:
===========
HTTPRequest Thread’s significance in HTTPChannel and handling SOAP events on HTTP Server.

Environment:
===========
TIBCO BusinessEvents 3.x
All Operating Systems

Resolution:
========
The first hit is always taken by the library thread. In built-in case you will see that the server internally spawns a thread/uses one from its pool and then following scenarios happen:

1). If the caller's thread is chosen, the same thread will be used to execute pre-processor and RTC.

2). If the workers/shared queue is used, the pre-processor and RTC are executed by one of the worker threads which are BE managed, but this also happens only after the server has picked up the request on its own thread. This is similar to how EMS also does. (EMS-Session-Dispatcher -> BE Worker)

To increase number of threads -
-------------------------------------
1). For the built-in case the be.http.maxProcessors can be used. The default is 5. Usually built-in case serves a lot of concurrent requests with very limited number of threads.      

2). This count sets number of IO workers the server needs to create. The number of concurrent requests is much more than those handled by traditional IO where one thread handles one request.

HTTPRequest Thread’s significance in HTTPChannel and handling SOAP events on HTTP Server.