Hi Ceriel,

> As soon as the virtuoso.log mentions "Exceeded maximum number of file 
> descriptors in FD_SET." 
> in a testing environment (=few users),
> how should the OS or virtuoso or the OS be reconfigured?

There are three posibilities:

1. Your ulimit / kernel settings are too small for your usage.

2. Your C library can only handle so many concurrent open file
   descriptors on a default compile. This is indicated by the FD_SETSIZE
   define in select.h. On Mac OS X this is a default of 1024, so
   if you have over 1024 concurrent files opened this can be an issue.

   Remember that all open connections count e.g. HTTP/ODBC/JDBC sessions
   as well as database files and temp streams.

   If this is the case, some header files allow you to set FD_SETSIZE
   to a larger value, but i would need to check if Apple can handle
   this.

3. You are experiencing a fd leak. I will send you a patch that could
   resolve this problem.


> /usr/local/virtuoso-opensource/var/lib/virtuoso/db/virtuoso.log
> ---
> 23:42:14 Checkpoint made, log reused
> 
>                 Mon Jan 18 2010
> 00:30:06 Exceeded maximum number of file descriptors in FD_SET.
> 00:42:16 Exceeded maximum number of file descriptors in FD_SET.
> 00:42:16 Checkpoint made, log reused
> 00:42:16 Exceeded maximum number of file descriptors in FD_SET.
> 00:42:17 Server received signal 11. Continuing with the default action for 
> that signal.
> 
>                 Mon Jan 18 2010
> 16:30:17 OpenLink Virtuoso Universal Server
> 16:30:17 Version 06.00.3123-pthreads for Darwin as of Jan 12 2010
> 16:30:17 uses parts of OpenSSL, PCRE, Html Tidy
> 16:30:29 Database version 3100
> 16:30:30 SQL Optimizer enabled (max 1000 layouts)
> 16:30:34 Compiler unit is timed at 0.002779 msec
> 16:30:37 Roll forward started
> 16:30:37     2 transactions, 87 bytes replayed (100 %)
> 16:30:37 Roll forward complete
> 16:30:39 Checkpoint made, log reused
> 16:30:42 HTTP/WebDAV server online at 8890
> 16:30:42 Server online at 1111 (pid 7403)
> 17:30:42 Checkpoint made, log reused


Patrick

Reply via email to