EMS server fails to start with exception "67 File descriptor limit".
book
Article ID: KB0084185
calendar_today
Updated On:
Products
Versions
TIBCO Enterprise Message Service
-
Description
When EMS is started on Windows, it creates dynamic ports on the loopback address (i.e [::1] for Ipv6).
For example, EMS 8.3 on Windows 7:
====== netstat -ano | grep 22476
TCP x.x.x.x:7222 0.0.0.0:0 LISTENING 22476 TCP [::1]:7222 [::]:0 LISTENING 22476 TCP [::1]:53015 [::1]:53016 ESTABLISHED 22476 TCP [::1]:53016 [::1]:53015 ESTABLISHED 22476 TCP [::1]:53017 [::1]:53018 ESTABLISHED 22476 TCP [::1]:53018 [::1]:53017 ESTABLISHED 22476 TCP [::1]:53019 [::1]:53020 ESTABLISHED 22476 TCP [::1]:53020 [::1]:53019 ESTABLISHED 22476 =======
If the above connections can not be created, the EMS server will not start and logs the exception, "FATAL: Unable to start Network IO Thread(s). Error: 67 File descriptor limit".
Environment
Windows
Resolution
1). Check the dynamic ports range on Windows 7 by using the commands below:
netsh int ipv4 show dynamicport tcp netsh int ipv6 show dynamicport tcp
Run "netstat -ano" to check the number of dynamic ports being used on the host.
Increase the range of dynamic ports if needed.
2). Run the Java sample attached (Filename: TCPServer.java) to check if the connection can be made to the loopback address.
Run the command below to confirm if the connection on the loopback address is created:
=== netstat -ano | findstr 49212 TCP [::1]:49212 [::1]:49215 ESTABLISHED 5896 TCP [::1]:49215 [::1]:49212 ESTABLISHED 5896 ===
If the connection fails to be created, it indicates that there is a configuration issue of the loopback address (i.e on Ipv6 [::1]) on the host. Consult your System Administrator or Microsoft Support.
Issue/Introduction
EMS server can not be started and logs the following exception: "FATAL: Unable to start Network IO Thread(s). Error: 67 File descriptor limit".
Additional Information
SR 01245415
Attachments
EMS server fails to start with exception "67 File descriptor limit".get_app