Problem with long running backend process - Page can not be displayed
Hi,
I have a probelm with a long running backend process. A web application is deployed on BEA Web Logic 8.1. When one of the forms is submitted, it takes around 2 hours for the web application to respond. It actually creates thousands of threads.
But the problem is after an hour, the browser shows 'Page can not be displayed'.
From the server logs I can see that the process is running and logs are getting produced.
I can't understand the reason behind the error. I think there is some configuration in the server to handle such long running processes (timeout or something). I have set the Inactive Connection Timeout to 0. But still I get the error.
Thanks in advance,
Balkrishna.
# 1
For this sort of long running process, it would be better to start off a seperate thread to handle the process, and then return a response saying "your job has been started. Check back later to see how things are going"
It avoids the timeout issue, and makes the program more user friendly.
Cheers,
evnafets
# 2
Hi evnafets,
Thanks for your reply.
I have exactly the same strategy in mind as you mentioned here. But before I do the changes, I would like to see the current implementation up and running.
It would be nice if you let me know some configuration setting that would be causing this.
One more interesting input is that if I run a small process (which takes around an hour to complete), I don't face this problem.
I appreciate your response.
Thanks,
Balkrishna.
# 3
Hi,
The problem is resolved.
Actually I am using Internet Explorer 6.0 which has a limit of 60 minutes for connection timeout. That is why it used to show 'Page cannot be displayed' after an hour.
http://support.microsoft.com/kb/181050/en-us
Now I can go ahead do the changes to make the process asynchronous.
Thanks,
Balkrishna.
