I have an application using Flex 3 and RTMP for real time updating running on CentOS and Tomcat 5.5. However, as this product has grown I am seeing an increasing problem with file descriptors. When the connection is close by any means the RTMP port is left open but changes state to "can't identify protocol" according to lsof. WHen I say "by any means" I mean actually closing the connection in flex with .close(), garbage collection, or network disconnect. This "can't identify protocol" remains open until tomcat is restarted. Because it remains open until tomcat is restarted eventually connections are refused because their are insufficient file descriptors. I have increased the number of allowed file descriptors but the problem is that is only a bandaid solution. As the program continues to grow I will have to continue to increase the number of file descriptors.
Does anyone have any thoughts on why this RTMP connection may be sticking around?
Does anyone have any thoughts on why this RTMP connection may be sticking around?