WebSEAL - sending over 100 requests in one tcp session.
Flash (Alert)
Abstract
We are not allowed to send over 100 requests continuously.
Content
When you send many requests, that each request is sent within persist-con-timeout seconds from the previous request, webseald will close the connection after receiving 100 requests.
We cannot send over 100 request in one tcp session. WebSEAL doesn't receive more than 100 requests at the same session. This is hard corded design. We cannot change this behavior.So, if you want to send more than 100 requests, your application have to re-negotiate a new tcp session.
Update: new parameter called connection-request-limit in [server] stanza is implemented. You can use this parameter to change the limit from:
5.1.0-TIV-AWS-FP0034
6.0.0-TIV-AWS-FP0015
6.1 GA
Update: Please note that one tcp session use one worker thread until all requests finished. If you set large value for this parameter, one thread need to handle many requests for a long time. This leads worker thread exhaustion if many sessions need to handle many requests in one session (if each of all requests are sent from client within persistent-con-timeout). You should set lower value (not 100) for worker-thread-(soft|hard)-limit to make webseald being able to return 503 error to clients.
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.
Rate this page
Please take a moment to complete this form to help us better serve you.
