We are using RC1 with Mina M4 and we start the server embedded in a tomcat 5.5.x webapp. Java is version 5.0 running on Linux. There was another user with the same "Max login" problem as I previously posted that problem to this group.
Even when the ftp server dies the tomcat server is running fine throughout, still taking connections etc. Once we reboot the ftp server starts working again. At this point my guess is there is somewhere in the login workflow where something isn't being closed properly. We have several users running batch scripts, if they aren't closing a connection etc. that should not be able to crash the ftp server. Maybe connections are not being closed or collected with an idle timeout in some cases? For now we are just going to restart the server and wait and see. Thanks, Dan -----Original Message----- From: West, John C [mailto:john.c.w...@citizensbank.com] Sent: April-06-09 2:00 PM To: ftpserver-users@mina.apache.org Subject: RE: Stability and reliability issues Well I'm using this server in a couple different production environments without any issues and I know there are others on this list who are as well, so I'd say your experience is not typical. What version of the ftp server and Java are you using? What operating system? The debug level is set in log4j.properties. -----Original Message----- From: Dan [mailto:d...@tipjarawards.com] Sent: Monday, April 06, 2009 1:51 PM To: ftpserver-users@mina.apache.org Subject: Stability and reliability issues We are having some serious stability/scalability issues with the ftp server. First there were hanging logins (nobody able to login but supposedly max login users was reacehd according to log message). With idle timeouts this should never happen as after a few minutes all the "dead" logins should have been collected. Second problem we are now getting 'Could not connect to server' and 'Connection timed out' errors with the server running after only two days. It gets as far as the "CREATED" log message then hangs as a user tries to connect and login. So we will be rebooting the server again as it appears the server is again dead. I hope the focus of development is first and foremost stability/reliability since adding in new features to a server that keeps crashing in a production environment is very troubling. I am happy to provide more debug info or log info to help, it's just not clear how to accomplish this. Where can I easily set the debug level? Any ideas? Let me know. Thanks, Dan ----------------------------------------- Use of email is inherently insecure. Confidential information, including account information, and personally identifiable information, should not be transmitted via email, or email attachment. In no event shall Citizens or any of its affiliates accept any responsibility for the loss, use or misuse of any information including confidential information, which is sent to Citizens or its affiliates via email, or email attachment. Citizens does not guarantee the accuracy of any email or email attachment, that an email will be received by Citizens or that Citizens will respond to any email. This email message is confidential and/or privileged. It is to be used by the intended recipient only. Use of the information contained in this email by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please notify the sender immediately and promptly destroy any record of this email.
