Steps 1. test.jsp page 2. user presses a button and calls servlet 3. Servlet calls database procedure in DAO 4. servlet forwards the request to same jsp page.
Following is the code in Servlet,
The requestdDispatcher does not work if the database procedure takes more than 10 mins. Please let me know how to rectify this. There is no error, browser just keeps loading and nothing happens. Debug messages before forward was written to the console. Database procedure executes fine.
As Bear suggested, you need to shorten the client wait time. 10 minutes is a very long time. Can you may be bring back partial information and then make another call to the database if the user indicates so. Most users will nto wait for 10 minutes anyway.
Bosun (SCJP, SCWCD)
So much trouble in the world -- Bob Marley
Joined: Jun 10, 2008
Thanks for your replies. I will try the one as you all said
the parameter for setMaxInactiveInterval is expressed in seconds, whereas the one in the deployment descriptor is in minutes.
When we configure session timeout in web.xml, it is applicable to all the sessions created.
When we call setMaxInactiveInterval(int interval) on a session object, then the timeout is set only for that specific session object.
If you have specified a timeout value in web.xml and also calling setMaxInactiveInterval(int interval) on a session object, then for that session object, value set in setMaxInactiveInterval() will be considered for timeout.
You should not do let it take that long time. Around max 3 seconds is an acceptable response time. Otherwise users will likely abort the request. I suggest to let run it in the background and if necessary inform the end user about the status using ajaxical polls.
Joined: Jan 30, 2009
Yes Bauke is Right.
Nobody will stick to your site if it takes such a long time .
This site is very much faster compared to sun site (sun takes a lot of time to login also) dont know why