• 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Jeanne Boyarsky
  • Devaka Cooray
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Knute Snortum
  • Bear Bibeault
Saloon Keepers:
  • Ron McLeod
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Ganesh Patekar
Bartenders:
  • Frits Walraven
  • Carey Brown
  • Tim Holloway

how solve error "The connection was reset" in my project and tomcat?

 
Ranch Hand
Posts: 54
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi

my project is running in tomcat (security manager) .
my project is working properly in my host for 8 or 9 day .
After this my project can not reply to request and my project need to restart .

when requested my project in browser get this error:
   The connection was reset
   The connection to the server was reset while the page was loading.


please help me
 
Author and all-around good cowpoke
Posts: 13078
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would certainly expect some useful information to show up in the Tomcat log files.

When this happens, do other Tomcat application continue to run?

Bill
 
amir taghvayi
Ranch Hand
Posts: 54
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
hi bill .

I've requested a log file of my host ?

my host says that other programs can work properly .
 
Bartender
Posts: 20836
125
Android Eclipse IDE Tomcat Server Redhat Java Linux
  • Likes 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It's nearly 100% certain that the failing application is defective and from the sound of it, it probably has a slow resource leak. Tomcat is very reliable, and when it does fail, it is almost always going to fail for all apps, not just one of them.

Slow resource leaks can take a certain amount of detective work. They often occur because of things like people forgetting to close files (or thinking that they don't have to), database exception handlers that don't close connections, cleanup services that don't actually clean up - causing the number of things being "cleaned" to get bigger and bigger". Stuff like that.

You'll probably need both Tomcat logs and application logs. I would also interview some of the users and see if they start seeing problems (slow response, error pages) that build up the longer the application has been running. That may give you an idea of where to investigate further.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!