aspose file tools*
The moose likes Servlets and the fly likes RequestDispatcher.forward does not work Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Servlets
Bookmark "RequestDispatcher.forward does not work" Watch "RequestDispatcher.forward does not work" New topic
Author

RequestDispatcher.forward does not work

arunkumar subramanian
Ranch Hand

Joined: Jun 10, 2008
Posts: 32
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.
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 60997
    
  65

The browser is likely timing out.

Shorten your cycle -- 10 minutes is a ridiculously long time to have a user stare at an unresponsive application. Heck, 10 seconds is a long time.

If you can't shorten the cycle, do the processing it in the background and let the user come back to see the results later.


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
arunkumar subramanian
Ranch Hand

Joined: Jun 10, 2008
Posts: 32
Thanks for your reply. Is there a way I can set time out in browser to be like 30 mins.
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 60997
    
  65

No. Besides, how would you get your users to do that?
Bosun Bello
Ranch Hand

Joined: Nov 06, 2000
Posts: 1510
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
arunkumar subramanian
Ranch Hand

Joined: Jun 10, 2008
Posts: 32
Thanks for your replies. I will try the one as you all said
kamlesh yadav
Greenhorn

Joined: Dec 04, 2008
Posts: 2
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.
RaviNada Kiran
Ranch Hand

Joined: Jan 30, 2009
Posts: 528
Try setting Headers like connection keep-alive and also set the parameter for connection Time out in your server also .

Let me know whats the server you are using ??I may help you.


If you want something you never had do something which you had never done
Bauke Scholtz
Ranch Hand

Joined: Oct 08, 2006
Posts: 2458
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.
RaviNada Kiran
Ranch Hand

Joined: Jan 30, 2009
Posts: 528
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
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: RequestDispatcher.forward does not work