Hi,
I've been experiencing issues when submitting forms using IE. I'm using
Wicket with Jetty under Windows.
Sometimes, when submitting a form the user sees a "session expired" page and
loses his data. When testing this I set the session-timeout to 60 minutes
and the problem appeared well before that (unfortunately I found no sure way
to reproduce this, apparently it is due to "imperfections" in our corporate
network)
In the logs, There is the following trace :
2008-03-26 17:07:11.163::WARN: /myapp/
wicket.WicketRuntimeException: Redirect failed
at wicket.protocol.http.WebResponse.redirect(WebResponse.java:209)
at
wicket.protocol.http.BufferedWebResponse.close(BufferedWebResponse.java:68)
at wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:229)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:367)
at
org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:285)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:502)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:821)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:208)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:378)
at
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:226)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: org.mortbay.jetty.EofException
at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:767)
at org.mortbay.jetty.HttpGenerator.complete(HttpGenerator.java:655)
at
org.mortbay.jetty.HttpConnection.completeResponse(HttpConnection.java:592)
at org.mortbay.jetty.Response.complete(Response.java:1074)
at org.mortbay.jetty.Response.sendRedirect(Response.java:398)
at wicket.protocol.http.WebResponse.redirect(WebResponse.java:203)
... 19 more
Caused by: java.net.SocketException: Connection reset by peer: socket write
error
at java.net.SocketOutputStream.socketWrite0(Native Method)
at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
at org.mortbay.io.ByteArrayBuffer.writeTo(ByteArrayBuffer.java:158)
at org.mortbay.io.bio.StreamEndPoint.flush(StreamEndPoint.java:114)
at org.mortbay.jetty.HttpGenerator.flush(HttpGenerator.java:695)
... 24 more
My guess is that the BufferedWebResponse does too much in the close()
method, and thus escapes the exception handling code normally done in
Resource.respond().
Any hints on how I can avoid or fix this ?
Thanks.
--
View this message in context:
http://www.nabble.com/Sometimes-get-%22Session-expired%22-when-submitting-forms-with-IE-tp16329201p16329201.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
