Article - CS271629
Configuring the open file descriptor limits (ulimit) settings for ThingWorx Platform running on Linux
Modified: 21-May-2024
Applies To
- ThingWorx Platform 7.3 to 9.3
- Linux
Description
- What are the correct ulimit -n settings when running ThingWorx in a Linux environment?
- How to set ulimit for ThingWorx
- How many file handles or file descriptors are required for ThingWorx to operate?
- Following errors are seen in Tomcat/logs/catalina.out:
- Error: Websocket is already in CLOSING or CLOSED state
- Error: Too many open files
- Remote things are getting disconnected at random from ThingWorx server
- Unable to initiate remote sessions or register any new Axeda devices
- Errors are seen in in ThingworxStorage/logs/ApplicationLog.log:
- Warn: Server WebSocket closed unexpectedly, unregistering from Server Endpoint [ws session id: xx, endpoint id: xx, endpoint name: Emessage-cxserver-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx] java.io.IOException: Broken pipe:
- Warn: Endpoint does not contain binding but Thing is already connected. Bind attempted with
- Error: Error trying to process message: Binding failed, see server log for more information
This is a printer-friendly version of Article 271629 and may be out of date. For the latest version click CS271629