SOAP Timeouts and thread pools in Tibco BW

Simple exercise: we spawn 400 processes calling WebService operation doing 1h sleep. With SOAP call timeout set to zero, we see 400 callers waiting and only 10 implementations running. This is because keep-alive is set at the TCP/IP level, no socket timeout is enforced and BW thread pool for SOAP request-responses has got default size of 10 threads. Whole solution hangs. In Designer console you can see that maximal WebService capacity is 75 parallel request by default.

Conclusion: don't rely on defaults, alway tune deployed BW component!