Petals BC SOAP

The max size of the pool of webservice clients should be defined according to the max number of JBI message processors

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Bug
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 4.0.9
Fix Version/s: 4.0.10, 4.2.0
Component/s: None
Security Level: Public

Description:
Hide
If we have the following sizing at BC SOAP level:

<ns2:acceptor-pool-size>5</ns2:acceptor-pool-size> <ns2:processor-pool-size>10</ns2:processor-pool-size> <ns2:processor-max-pool-size>50</ns2:processor-max-pool-size>

The max size of the pool of webservice clients is set to the value of acceptor-pool-size. So if we send 15 requests concurrently to the same external service, we can have more than 10 requests processed concurrently, at BC SOAP level.

The max size of the pool of webservice clients should be set to the value of processor-max-pool-size.

(Thanks to tests about the POC of monitoring probes)
Show
If we have the following sizing at BC SOAP level:

<ns2:acceptor-pool-size>5</ns2:acceptor-pool-size> <ns2:processor-pool-size>10</ns2:processor-pool-size> <ns2:processor-max-pool-size>50</ns2:processor-max-pool-size>

The max size of the pool of webservice clients is set to the value of acceptor-pool-size. So if we send 15 requests concurrently to the same external service, we can have more than 10 requests processed concurrently, at BC SOAP level. The max size of the pool of webservice clients should be set to the value of processor-max-pool-size. (Thanks to tests about the POC of monitoring probes)

Environment:

-

Activity

People

Assignee:

Christophe DENEUX

Reporter:

Christophe DENEUX
Watchers:

0

Dates

Created:

Thu, 26 Jan 2012 - 15:56:43 +0100

Updated:

Mon, 12 Mar 2012 - 11:28:54 +0100

Resolved:

Mon, 12 Mar 2012 - 11:16:18 +0100