According to my perception, this error occurs if you submit a request, and before getting the response, you submit it once again. A workaround might be using javascript to avoid multiple submissions of requests.
----- Original Message ----- From: "Jan Aren�" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, April 22, 2002 4:44 PM Subject: Re: Passing parameters from a page to another > I have some more data for you. > > Since this paged worked before I tried to change it back step by step. And > if I do a <jsp:foward> instead of a response.sendRedirect() it work fine. > The problem is that I dont want to do a forward (since if they do a reload > page the data is stored once again etc.) > Does anyone have a clue why the server/client behave like this? > > /Jan > > -----Ursprungligt meddelande----- > Fr�n: A mailing list about Java Server Pages specification and reference > [mailto:[EMAIL PROTECTED]]F�r Jan Aren� > Skickat: den 22 april 2002 11:58 > Till: [EMAIL PROTECTED] > �mne: Passing parameters from a page to another > > > Hi all > > I discovered a problem that I didn't know I had... > I have a "big" form on a page with 97 input boxes. > They are all called id followed by a number. (eg id1, id2 ...) > > I submit the form as a POST-method to another page. > There I read all the inputboxes and store it in a Vector that I passed to a > bean. > > Somewhere on this page something goes wrong! I'll get an error, that is not > shown as usual > > og3: java.net.SocketException: Connection reset by peer: socket write error > void java.net.SocketOutputStream.socketWrite(byte[], int, int)log3: > void java.net.SocketOutputStream.write(byte[], int, int)log3: > void oracle.lite.web.JupOutputStream.flush()log3: > void oracle.lite.web.JupHeader.write(java.io.OutputStream, > java.lang.String)log3: > void > oracle.lite.web.JupOutputStream.writeHeaders(oracle.lite.web.JupHeader, > java.lang.String)log3: > void oracle.lite.web.JupResponse.writeHeaders()log3: > void > oracle.lite.web.JupOutputStream.sendRedirect(java.lang.String)log3: > void oracle.lite.web.JupResponse.sendRedirect(java.lang.String)log3: > void > store_bokning._jspService(javax.servlet.http.HttpServletRequest, > javax.servlet.http.HttpServletResponse)log3: > void > oracle.jsp.runtime.HttpJsp.service(javax.servlet.ServletRequest, > javax.servlet.ServletResponse)log3: > void > oracle.jsp.app.JspApplication.dispatchRequest(javax.servlet.http.HttpServlet > Request, javax.servlet.http.HttpServletResponse)log3: > void > oracle.jsp.JspServlet.doDispatch(oracle.jsp.app.JspRequestContext)log3: > void > oracle.jsp.JspServlet.internalService(javax.servlet.http.HttpServletRequest, > javax.servlet.http.HttpServletResponse)log3: > void > oracle.jsp.JspServlet.service(javax.servlet.http.HttpServletRequest, > javax.servlet.http.HttpServletResponse)log3: > void > javax.servlet.http.HttpServlet.service(javax.servlet.ServletRequest, > javax.servlet.ServletResponse)log3: > void oracle.lite.web.JupServlet.service(oracle.lite.web.JupRequest, > oracle.lite.web.JupResponse)log3: > void > oracle.lite.web.MimeServletHandler.handle(oracle.lite.web.JupApplication, > java.lang.String, int, oracle.lite.web.JupRequest, > oracle.lite.web.JupResponse)log3: > void > oracle.lite.web.JupApplication.service(oracle.lite.web.JupRequest, > oracle.lite.web.JupResponse)log3: > void oracle.lite.web.JupHandler.handle(oracle.lite.web.JupRequest, > oracle.lite.web.JupResponse)log3: > void oracle.lite.web.HTTPServer.process(oracle.lite.web.JupRequest, > oracle.lite.web.JupResponse)log3: > boolean > oracle.lite.web.HTTPServer.handleRequest(oracle.lite.web.JupInputStream, > oracle.lite.web.JupOutputStream)log3: > boolean > oracle.lite.web.JupServer.handle(oracle.lite.web.JupInputStream, > oracle.lite.web.JupOutputStream)log3: > void oracle.lite.web.SocketListener.process(java.net.Socket)log3: > void oracle.lite.web.SocketListener$ReqHandler.run() > > > It seams like the socket gets "overloaded" or something? Is there a way to > work around this? > Notice that this do NOT occur everytime, just 1 of 3-4 maybe. > What happend is that I store all of this into a database. When the error > occur some of the posts get stored 2 times. Either in the beginning or in > the end (how many is "random") > > The bean does the following things : > 1. Deletes ALL data in table > 2. Store the 97 fields > > I can't find that this error depends on something else then that error. When > not error, everything runs fine. > > Please help > > Jan Aren� > > =========================================================================== > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff > JSP-INTEREST". > For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST > DIGEST". > Some relevant FAQs on JSP/Servlets can be found at: > > http://archives.java.sun.com/jsp-interest.html > http://java.sun.com/products/jsp/faq.html > http://www.esperanto.org.nz/jsp/jspfaq.jsp > http://www.jguru.com/faq/index.jsp > http://www.jspinsider.com > > =========================================================================== > To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". > For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". > Some relevant FAQs on JSP/Servlets can be found at: > > http://archives.java.sun.com/jsp-interest.html > http://java.sun.com/products/jsp/faq.html > http://www.esperanto.org.nz/jsp/jspfaq.jsp > http://www.jguru.com/faq/index.jsp > http://www.jspinsider.com =========================================================================== To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST". For digest: mailto [EMAIL PROTECTED] with body: "set JSP-INTEREST DIGEST". Some relevant FAQs on JSP/Servlets can be found at: http://archives.java.sun.com/jsp-interest.html http://java.sun.com/products/jsp/faq.html http://www.esperanto.org.nz/jsp/jspfaq.jsp http://www.jguru.com/faq/index.jsp http://www.jspinsider.com
