This morning we had an issue with openfire where users were not able to login. after inspecting the logs and some talented work by our technical team it was discovered that the cause was too many open file handles. The relevant log entry was:
2007.12.18 08:23:05 org.jivesoftware.openfire.ldap.LdapGroupProvider.getGroup(LdapGroupProvider.java :107)
javax.naming.CommunicationException: tos-dc4.thinkorswim.com:389 Root exception is java.net.SocketException: Too many open files
The ulimit for the server(jabber) was 1024
Pid of jabber was 11985:
root@chat:/opt/openfire/openfire/logs# ls -l /proc/11985/fd | wc -l 1025
Oops.
An ls -l /proc/28732/fd showed hundreds of:
lr-x------ 1 jabber jabber 64 2007-12-18 08:25 994 -> /tmp/MSN66084.dat
lr-x------ 1 jabber jabber 64 2007-12-18 08:25 995 -> /tmp/MSN66083.dat
lr-x------ 1 jabber jabber 64 2007-12-18 08:25 996 -> /tmp/MSN66092.dat
lr-x------ 1 jabber jabber 64 2007-12-18 08:25 997 -> /tmp/MSN66085.dat
lr-x------ 1 jabber jabber 64 2007-12-18 08:25 998 -> /tmp/MSN66098.dat
lr-x------ 1 jabber jabber 64 2007-12-18 08:25 999 -> /tmp/MSN66093.dat
root@chat:/tmp# file MSN8874.dat
MSN8874.dat: PNG image data, 96 x 96, 8-bit/color RGBA, non-interlaced
We have now increased the ulimit to 64k but this is a stop-gap unless we know that the Plugin (or the server) will eventually release the file handles.
I look forward to the response.