Article - CS335904
Configuring the open file descriptor limits (ulimit) settings for eMessage Connector running on Linux
Modified: 23-Sep-2022
Applies To
- ThingWorx Platform 8.5 to 9.3
- Linux
Description
- What are the correct ulimit -n settings when running eMessage Connector in a Linux environment?
- Setting ulimit for eMessage Connector (EMC)
- How many file handles or file descriptors are required for eMessage Connector to operate
- Error: Websocket is already in CLOSING or CLOSED state
- Error: Too many open files
- emessage.log shows the following:
- WARN i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
java.io.IOException: Too many open files
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422)
- WARN i.n.channel.DefaultChannelPipeline - An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.
- Unable to initiate remote sessions or register any new Axeda devices and ThingWorx Application.log shows the following:
- 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 335904 and may be out of date. For the latest version click CS335904