Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

HTTP 500 Internal Server Error

Status
Not open for further replies.

vinzmen

Programmer
Oct 1, 2010
2
GB
Hi All,

I have a server based application created in Delphi which allows the client to download financial reports from my web page. The reports are created according to the inputs (Start and End Date) supplied by the user. If the user requests information for a large period of time (say over 3 months of data) the web server causes the ‘HTTP 500 Internal Server Error’. However data requested for three months or less works fine. The server based application does take a long time (2-4 min) to create these reports as it goes through several functions and procedures.

If I were to remove certain functions or procedures from the main code it works regardless of the time period and creates the reports for the user to download. However these functions/procedures are required to create the complete report and hence cannot be omitted from the code. What i don’t understand is the fact that this works when data is requested for short interval of time and not for longer intervals which takes nearly 4 min to bring the HTTP 500 Internal Server Error web page. It looks like when the server based application is called to create the report (which it does – the loading bar at the bottom of Internet explorer progress slowly ) it runs in the background and finally when its ready to be send as an attachment for the user to download it loses its Response property or something.

I have been playing with this for over a week to find a way around this problem. Does anybody have any idea on how I can over come this issue?

I use Apache HTTP server.

Regards,
Vinzmen
 
It's hard to help you on this issue without more concrete information. Try to build in logging into your webapplication to see what it is doing (and were it is going wrong).

can you post the header information offthe answer from a request to your webservice?

both a working and faulty header could provide more insight.
You can collect this information with FireFox and it' FireBug extension for example.

/Daddy



-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top