From the initial email it seemed as though it's a two stage process (stage 1 : generate, stage 2 : export), hence I thought it possible that an idle time out could occur during the generation phase.

One approach I've seen is that a servlet starts the generation and lets the user carry on with their interaction with the webapp. Once the generation is complete the user is emailed a link where they can download the generated file. All this would, of course, need the necessary security put over the top to ensure users didn't download each others files.

Al.

Laurie Harper wrote:
Al Sutton wrote:
You may find that your app server, the clients browser, or any proxy in-between may timeout irrespective of what you do in your webapp.

If the timeout occurs during the PDF generation, before the response begins being streamed back, maybe. But as long as there is response data being transmitted, no timeout should occur at the connection level. A session timeout is an app-server function, anyhow; clients and proxies know nothing about the session.

Simon, is the timeout occuring during the request for the PDF, while it is being generated and before the action begins transmitting it? Or is the PDF downloaded successfully with the next request failing because the session timed out during the download?

L.

If the file takes so long to generate is there any reason why your not pre-generating it, caching it and serving it as a static file?

Al.

----- Original Message ----- From: "Simon Sew" <[EMAIL PROTECTED]>
To: <user@struts.apache.org>
Sent: Thursday, May 22, 2008 7:32 AM
Subject: Request/session timeout when exporting very large files


Hi,
I'm having this request/session timeout problem.

My page have a link to generate and export pdf file. The problem is sometimes the generated file is very huge (100MB++) and it takes quite some time to export it (30 to 90 minutes). How do I prevent it from timeout when it is exporting at that time?

I tried session.setMaxInactiveInterval() but it's not working.

Thx.



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to