Web cahce cannot start

Question

I failed to start web cache on solaris.
Some info in log:
04/Sep/2001:17:54:41 -0500 -- Error: Could not increase number of file/socket descriptors to 1050.
04/Sep/2001:17:54:41 -0500 -- Error: Failed to start the server.
Does anyone give a suggestion?
Thanks
Eric

Answer 1

See section 5 of the v2.0.0.0 or v2.0.0.1 readme. It says:
5.0 Connection Limitations
5.1 Unix
On most UNIX platforms there is a hard limit to how many file descriptors a process can open. This number is normally 1024 but is configurable. To be able to
change this default to a higher one, you have to be root or run the process as root. The other way is to set the setuid bit for the process to root. The procedure for
doing this is the same as listed below in section 10.0 "How to Configure Oracle Web Cache to Listen on Port <1024".
In this release, Oracle Web Cache calculates the maximum number of file descriptors to be used by using the following simple formula:
Max number of file descriptors to be used = Current Maximum Incoming Connections (specified in the webcache.xml through the Web Cache Manager
interface) + sum of Capacity for all the configured origin Web Server instances + 20 (reserved for internal use).
Based on the above formula the Web Cache server tries to reserve this many file descriptors at startup time. In case it fails to do so, it doesn't default to a lower
value but logs an error message and fails to start. In case the Web Cache server fails to start because the number of file descriptors required is more that 1024,
either run it as root or setuid the execuable to root.
Also, always set the "Current Maximum Incoming Connections" in Web Cache Manager to reflect correctly the maximum number of clients you intend to serve
concurrently at any given time. The value should not be set to an arbitrary high value, as Web Cache sets aside some resources for each and the performance
would be adversely affected.
5.2 Windows
On Windows NT Server and Windows 2000, the number of file handles as well as socket handles is limited only by available kernel resources, more precisely, by
the size of paged and non-paged pools. But the number of active TCP/IP connections is limited. In Windows NT the system starts to reuse TCP Control Blocks in
TIME-WAIT when the number of active connections goes over 1000. Windows NT 4.0 Service Pack 3 increased this threshold to 2000.
Windows NT Workstation is limited to 5 concurrent connections. Oracle Web Cache is not designed to run on Windows NT Workstation.