Hi..
Previously I thought it was session timeout, therefore I set a higher session
timeout value.
I tried to generate the pdf file again, this time it still timeout but it
haven't reach the threshold yet.
So, I can confirm it's request timeout.
I tried to use a dummy ajax which keeps refreshi
Are we talking about a *session* timeout or a *request* timeout? You
original message implied the former, since you were trying to correct it
with session.setMaxInactiveInterval(), but if it's a request timeout
that's not going to have any effect.
It sounds like the PDF generation is taking to
The request timeout occurs when it is still generating the pdf. When it
finished, the file will be exported to the jsp.
Laurie Harper <[EMAIL PROTECTED]> wrote: Al Sutton wrote:
> You may find that your app server, the clients browser, or any proxy
> in-between may timeout irrespective of what
Hmm...
I will try that.
Thx.
Owen Berry <[EMAIL PROTECTED]> wrote: How about having a DOJO remote div that
refreshes, thereby keeping the
session active. Could even show progress on the pdf generation.
On Thu, May 22, 2008 at 8:23 AM, Simon Sew wrote:
> Because we are required to generate the p
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
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
How about having a DOJO remote div that refreshes, thereby keeping the
session active. Could even show progress on the pdf generation.
On Thu, May 22, 2008 at 8:23 AM, Simon Sew <[EMAIL PROTECTED]> wrote:
> Because we are required to generate the pdf in real time. The data will
> always be chang
Because we are required to generate the pdf in real time. The data will always
be changing from time to time,therefore not suitable to be pre-generated.
Al Sutton <[EMAIL PROTECTED]> wrote: You may find that your app server, the
clients browser, or any proxy
in-between may timeout irrespective
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 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 Mes
9 matches
Mail list logo
