• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

HTTP Request Timeout / Keep - Alive

 
Ranch Hand
Posts: 49
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
We have a situation where environment has Webseal between the end user PC i.e. the client browser and web application. When user sends in a request, request goes thru Webseal to web app server. Webseal gives application 2 minute to send a response back to satisfy request. But in our application, for complex actions, it will frequently exceed 2 min to send response.

The requirement is to send a communication ping between end user and web application thru this connection to continually reset the clock that Webseal keeps ticking on the connection.

Has anybody ever faced such a situation or come across this before. Any suggestion will be helpful. This is highly critical for us.
 
Sheriff
Posts: 13411
Firefox Browser VI Editor Redhat
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a sample project on my site that handles this by kicking of the long running process in a new thread, and returning a response immediately.
The response page has a meta refresh tag in it that causes it to refresh every n seconds; checking the status of the long running process with each iteration. When the process is done, it forwards to the results page.

See: http://simple.souther.us/not-so-simple.html
Look for LongRunningProcess.

Also, for processes taking more than 15 or 30 seconds, you might want to consider implementing an email notification so the user doesn't have to sit and wait for the process to complete.
 
reply
    Bookmark Topic Watch Topic
  • New Topic