FAQs (EN)

17. From time to time I get the error message "Connection timed out" or "Read timed out" or socket server processes terminate. How can I prevent this?

• Due to the server load, waiting for the server response takes too long and the network connection is terminated.
• The configuration parameter de.cib.docserv.socket.SocketServerProcess.SocketTimeout has too small a value. You can use it to set the time to wait for the response from the executing socket servers.
• The socket servers terminate regularly because the configuration parameter de.cib.docserv.socket.SocketTimeout is set to a value greater than 0. With the configuration parameters de.cib.docserv.socket.SocketServerProcess.ConnectWait and de.cib.docserv.socket.SocketServerProcess.ConnectMaxTries you can try to connect to the socket servers longer/more often.
• The socket servers terminate unnecessarily and must be restarted, because the /Idle call parameter has a too small value. For example, increase the value to 1h by setting the configuration parameter de.cib.docserv.socket.IdleShutdownTime to 3600. The entry "nnnnn seconds elapsed without an incoming request - shutting down" can be found in socketserver.log.
• The socket servers have shut down due to an unexpected error. Please activate all log files, reproduce the behaviour and transfer them together with all other required files (templates, jobconfig.xml, application server log) to CIB support.