This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
on the login page where user puts in user name and password, when i hit the submit button couple of times quickly without filling userid and password, i get java.net.SocketException. Connection reset by peer. I am using Tomcat as web server. My hunch is that since Tomcat is not able to handle so many hits, thats why i am getting this error. But i am not sure as to why i am getting this error. If sb could tell me how many hits can tomcat take successfully. and can i configure Tomcat to take more hits ?? if yes where can i do that ? thanks to all of you in advance
Hi William , 1.Can U shed some light on browser connection 2.what can make the browser close the connection 3.How can this error be avoided All ideas are welcomed. [ May 12, 2002: Message edited by: Gabriel Fox ]
Hi... This is the problem we faced. This happened when we are using MVC architecure for our portal. What happened is when submitted twice requests are sent to same controller and controller is not thread safe.. So shared objects like session objects, Application objects are corrupted and when these corrupoted objects (Usually value beans stored in session/Application)are used in JSP code this exception is thrown.. We resolved this problem by disabling submit button after submission.. One more solution is making servlet and other related components thread safe by implementing SingleThreadModel but this may pose a serious performance problems. Hope this helps.. Rgds Manohar
Joined: Oct 17, 2001
Cheers guys for the solid info. Nice reference on connection-reset by peer i have confirmed it's true nature from the Tomcat conf directory.