On Tuesday, June 25, 2013 4:51:33 PM UTC-5, jhulford wrote:
It's because the browser is closing the connection, that's what the wrapped exception means. The user is either hitting the stop button or navigating away or the file you're writing is taking way too long to write out and the browser (or a proxy along the way) is closing out the socket before everything is written.--
You probably need to run this csv process in a background processing queue of some sort.
On Monday, June 24, 2013 3:43:40 PM UTC-5, Shashank Beerla wrote:Can anyone please suggest how to resolve this exception. I implemented a code which writes huge data to the csv file. I don't know why the connection is getting out.org.mortbay.jetty.EofExceptionorg.mortbay.jetty.EofExceptionorg.mortbay.jetty.HttpConnection$Output@f09f9a at org.mortbay.jetty.HttpGenerator.flush( HttpGenerator.java:760) at org.mortbay.jetty.AbstractGenerator$Output. flush(AbstractGenerator.java: 566) at org.mortbay.jetty.HttpConnection$Output.flush( HttpConnection.java:911) at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java: 297) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java: 229) at java.io.BufferedWriter.flush(BufferedWriter.java:254) at com.fedex.forecast.datamart.server.util. CSVFileDownloadServlet. writeCsv( CSVFileDownloadServlet.java: 180) at com.fedex.forecast.datamart.server.util. CSVFileDownloadServlet.doPost( CSVFileDownloadServlet.java: 75) at com.fedex.forecast.datamart.server.util. CSVFileDownloadServlet.doGet( CSVFileDownloadServlet.java: 38) 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:362) 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:729) at org.mortbay.jetty.webapp.WebAppContext.handle( WebAppContext.java:405) at org.mortbay.jetty.handler.HandlerWrapper.handle( HandlerWrapper.java:152) at org.mortbay.jetty.handler.RequestLogHandler.handle( RequestLogHandler.java:49) at org.mortbay.jetty.handler.HandlerWrapper.handle( HandlerWrapper.java:152) at org.mortbay.jetty.Server.handle(Server.java:324) at org.mortbay.jetty.HttpConnection.handleRequest( HttpConnection.java:505) at org.mortbay.jetty.HttpConnection$RequestHandler. headerComplete(HttpConnection. java:829) at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:513) at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser. java:211) at org.mortbay.jetty.HttpConnection.handle( HttpConnection.java:380) at org.mortbay.io.nio.SelectChannelEndPoint.run( SelectChannelEndPoint.java: 395) at org.mortbay.thread.QueuedThreadPool$PoolThread. run(QueuedThreadPool.java:488) Caused by: java.io.IOException: An existing connection was forcibly closed by the remote hostat sun.nio.ch.SocketDispatcher.write0(Native Method) at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java: 51) at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil. java:94) at sun.nio.ch.IOUtil.write(IOUtil.java:51) at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java: 450) at org.mortbay.io.nio.ChannelEndPoint.flush( ChannelEndPoint.java:160) at org.mortbay.io.nio.SelectChannelEndPoint.flush( SelectChannelEndPoint.java: 207) at org.mortbay.jetty.HttpGenerator.flush( HttpGenerator.java:693) ... 28 more
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment