Title: [jdjlist] Long Report
You could use a different approach that also works in a cluster:
 
1. the client browser requests the java servlet
2. the java servlet generates a machine dependent url, starts a thread with the request to the app server including the url and returns the url to the client.
3. you could store the state of the report in a database (is it available on the servlet server or not) and have a jsp-page checking this state and using javascript to refresh itself until the report is available. then it would display the url or open it directly.
4. the thread started in 2. simply waits for the app server to return the report and then stores it in the url specified.
 
You don't need to expose your internal structure if you have a rule based load balancer like resonate. You have one virtual ip for the cluster and then generate rules to dispatch certain urls to certain servers (www.mydomain.com/reports1/* -> server1, www.mydomain.com/reports2/* -> server2). If you don't have a rule based load balancer, you include the server name directly in the url returned to the browser: www.server1.com/reports, www.server2.com/reports so that these requests will pass through the load balancing.
 
Of course, you need to clean up the report directories regularly, e.g. using a "cron" or "at" job to remove old files.
 
Regards
Kim

[Lesden, Kim]  -----Urspr�ngliche Nachricht-----
Von: Greg Nudelman [mailto:[EMAIL PROTECTED]]
Gesendet: Mittwoch, 31. Juli 2002 00:11
An: JDJList
Betreff: [jdjlist] Long Report

Question for the Gurus:

I got a Java App server sending a long HTML report (2-5 Mb) to the Java Servlet and Java Servlet (Apache JServ) then sends it to the client.  I am seeing a very strange IE 5.50 behavior:

1) IE POST (client waits ~5 min)
-- about 50% of the info comes back
2) Weird: IE automatically re-posts the request (client waits ~5 min AGAIN!)
-- some info comes back (100%?)
3) Weird: Immediately, IE issues a GET
-- servlet immediately replies: "400 GET not supported"

I got to use IE, but for some strange reason, IE decides to refresh and make the user wait another 5 minutes for this report, and then of, course GET breaks it altogether.  BTW: Tried it with Netscape 6.2, it hangs on trying to parse this size of HTML file, but it does not re-issue a POST and does not produce a GET.

I have some options, but they are very limited:

can't send them the report in the email
can't request report via GET
can't produce a report and store it in the web folder for later, as I have multiple concurrent machines that do not share hard drive space.

can't make it return faster then 5 min

CAN TRY to make it return a zip file from the POST.

Has anyone run into this IE issue and does anyone know a way to get the users a secure long HTML report in a sensible fashion?

Thanks in a advance,

Greg

To change your membership options, refer to:
http://www.sys-con.com/java/list.cfm
To change your membership options, refer to:
http://www.sys-con.com/java/list.cfm

Reply via email to