Yes, the Linux soft and hard open files limits can greatly affect TDV Server's operations, negating the access to files TDV needs to open to either write or read from them.
This limit is usually set system wide, and will be shared by other processes.

TDV will notify in the cs_server.log about this issue and performance and stability problems will arise.

 

ERROR [DbChannel-RequestSelectThread] 2023-10-17 14:44:22.902 +0000 RequestSelectThread - Failed to accept client connection.[dbchannel-1918039]  [dbchannel-1918039]
	at com.compositesw.server.dbchannel.RequestSelectThread.run(RequestSelectThread.java:417)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: java.io.IOException: Too many open files
	at java.base/sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
	at java.base/sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:533)
	at java.base/sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:285)
	at com.compositesw.server.dbchannel.RequestSelectThread.run(RequestSelectThread.java:383)
	... 3 more

To remedy this, please review your Linux machine settings, as well as the current TDV Server I/O load, and if there are other applications running in the same machine and the amount of files opened by these other applications.

The commands to check the limits in Linux are the following:

           For hard limit: ulimit -Hn
           For soft limit  : ulimit -Sn

To check the maximum number of open files that can be opened in the current active session:

       cat /proc/sys/fs/file-max

To change the system-wide maximum open file limit, Execute the following command: sysctl -w fs.file-max=xxxxx
       To change the hard limit:  ulimit -Hn xxxxx
       To change the soft limit:  ulimit -Sn xxxxx

Where the xxxxx represent the required value.

Usually the principal reasons for this kind of error come from using performance analysis software such a Jmeter or concurrent file intensive TDV Server operations such as caching of resources, complex queries opening multiple tables in the repository and high user load.