• 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 ...
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
  • Mikalai Zaikin


Posts: 2
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a "TCP_ERROR" problem while connecting to a website.
Am connecting to website on a server say X from client machine using a IE browser with the site URL requesting for a page. As per the process, at this moment, the web-server connects to the database server say Y via APIs and does some backend data processing in Server X which takes about 20-30 minutes. By that time, on the client machine I get the "TCP_ERROR".
Basically, the IE browser (Client) cannot wait until the Server returns the data to the page.
How do I resolve the "TCP_ERROR" problem ?
On Server X, am using JAKARTA-TOMCAT-4.1.24 as web server.
Operating System as Window NT 5.0 Build
Memory of 1024 MB

Ranch Hand
Posts: 3695
IntelliJ IDE Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
stop waiting?

But seriously.. if you're just using the browser to 'launch' an extremely long-running process, you could try spawning a new Thread to do the long process, and use some sort of 'polling' to determine if the job is done. That is...
1) request the URL that launches the process.
2) after any 'setup work' (like authorization, connections, etc) launch a thread to do the processing.
3) forward to a JSP page that uses HTML meta refresh tags to...
4) request a 'status' page. This page will query some area that will be used by the Thread you launched, to notify the user that the process is "done".
5) If not done, then reload the meta refresh page, else.. load a 'finished' page

The 'area' could be the Session, or a database, or a file.
[ February 25, 2004: Message edited by: Mike Curwen ]
Don't get me started about those stupid light bulbs.
    Bookmark Topic Watch Topic
  • New Topic