I have been running some servlet tests on my WIn-95 system until I can set up an
NT dedicated server.
Each evening I restart the servletrunner (JSDK 2.0) and let a few people (about
10) try out the query system it supports.
Usually by mid morning the next day, the system has hung. When I look at it in
the evening, it shows no Java errors, or unusual queries: the servlet has just
stopped responding. You must Ctrl/C out and restart the servletrunner.
The servletrunner has not destroyed the servlet because I have a print message
there as well.
Is this a known problem with servletrunner? Is this why you need to buy a real
server: because it doesn't run reliably, or could there be fundamental error in
the servlet that is causing the hang?
James W. Cooper
Advanced Information Retrieval and Analysis
IBM T J Watson Research Center
[EMAIL PROTECTED]
http://flahdo.watson.ibm.com/
http://www.research.ibm.com/people/j/jwcnmr/
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
