Chapter 5 Section 5.6
Configuring the HTTPS eWay Setting Acceptor Threads Property for HTTPS Server Mode
HTTPS eWay Adapter User’s Guide 54 Sun Microsystems, Inc.
5.6 Setting Acceptor Threads Property for HTTPS Server
Mode
Before you run the Java CAPS Logical Host, you must set the Acceptor Threads
property for the Sun SeeBeyond Integration Server HTTP listener. This property allows
you to set up the correct performance of the HTTPS eWay in server mode.
Acceptor threads operate as follows:
At server start-up time, the Sun SeeBeyond Integration Server HTTP listener
creates a number of request-processing threads. Each incoming request requires a
thread for the duration of that request.
If more simultaneous requests are received than can be handled by the currently
available request-processing threads, additional threads are created. This number is
limited by the configured maximum.
If still more simultaneous requests are received, they are queued inside the server
socket created by the HTTP listener, up to the configured maximum. Any further
simultaneous requests receive “connection refused” errors, until resources are
available to process the requests. In Java CAPS, such errors appear in the log file for
the server mode eWay component.
Note: For more information, visit the Apache Tomcat server, version 4.1, Web site.
To adjust the number of threads that wait for HTTP connections (Acceptor threads)
according to the needs of your application, refer to the Sun SeeBeyond eGate™
Integrator System Administration Guide for more information.