-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thomas,
On 11/10/2009 2:53 AM, thomas2004 wrote: >> Just to confirm: you have a single request that takes 20-40 minutes to >> fulfill? Or do you issue a request to generate the report and then, >> later, issue a request to retrieve the (already-generated) report? > > I issue a request to generate the report (click the button "Create Report") > which is done in Jboss. The report-generation takes very long since it will > hold data from the database and process them. As the Jboss sends back the > PDF-report stream back to the browser, it failed. From the log message this > means the way return to client (browser) is closed. The client probably hung up the phone because it takes 20-40 minutes to respond to the request. 20-40 minutes is an unreasonable amount of time to wait for an HTTP request to complete. I recommend changing your architecture so that HTTP requests don't have to take so long. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkr5zlEACgkQ9CaO5/Lv0PCTFACfYde1O1nUrA7MDvA6RSZtol7M XdUAniqmFzB2G/bm6rY3aqnU5SJxy4vK =Qp8v -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
