Oracle iPlanet Web Server Crashes On Startup When The Operating System File Descriptor Limit Is Very High (Doc ID 1391473.1)

Last updated on JANUARY 13, 2017

Applies to:

Oracle iPlanet Web Server - Version 7.0 to 7.0 [Release 7.0]
Information in this document applies to any platform.
***Checked for relevance on 20-Jan-2014***

Symptoms

Oracle iPlanet Webserver 7.0 getting crashed and dumping core file while starting.

With finest logging will see messages in webserver error log file as follows:


[29/Dec/2011:18:42:04] fine (24683): Installed configuration 1
[29/Dec/2011:18:42:04] fine (24683): operating system file descriptor limit is 2147483647
[29/Dec/2011:18:42:04] fine (24683): allocating 536870912 file descriptors to the connection queue, 1073741824 file descriptors to keep-alive connections, and 1024 file descriptors to the file cache
[29/Dec/2011:18:42:04] fine (24683): HTTP3064: HTTP keep-alive timeout is 30 seconds
[29/Dec/2011:18:42:04] fine (24683): Async accelerator cache is On
[29/Dec/2011:18:42:04] fine (24683): Initialized accelerator cache
[29/Dec/2011:18:42:04] fine (24683): 1610612864 connection maximum (536870912 queued, 128 active, 1073741824 keep-alive)
[29/Dec/2011:18:42:05] fine (24683): Updating accelerator cache
[29/Dec/2011:18:42:08] catastrophe (24683): CORE3260: Server crash detected (signal SIGSEGV)
[29/Dec/2011:18:42:08] info (24683): CORE3262: Crash occurred in function ConnectionQueue::ConnectionQueue(const unsigned,const uns
igned) from module /u820/webserver7/lib/libns-httpd40.so
[29/Dec/2011:18:44:46] fine (24682): CORE3061: received signal 18
[29/Dec/2011:18:44:46] fine (24682): CORE3049: Detected child process 24683 died (status 139)
[29/Dec/2011:18:44:46] fine (24682): CORE3071: Child died before completing init

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms