Joseph,
Thanks for writing. I'm aware of the artificial connection-limit inder
W2KPro, but we are running the server product, which admittedly is the
Pro product with a few Registry changes and a few things like Terminal
Server tacked on. In any case, I don't think we're running into the
problem
Do you know if a request might be accessing the JSP page while
another request is trying to compile the updated version?
Also, I assume if it is not found through Apache, it is also
not found accessing Tomcat directly?
Cheers,
Larry
-Original Message-
From: David Bank [mailto:[EMAIL
Larry,
Thanks for writing. Right now, our environment is mostly a development
one, and very few people access our servers. And the problem has also
occurred on our development box, which only the programmer tests
against. So, we're reasonably sure that the situation you describe is
not
I have seen similar behaviour before on a Win2K box, but it was a Win2K
professional computer. The problem is that Win2K pro only allows a certain
number of incoming connections, I believe 10. We saw this during unit
testing of components when developers were testing on their own computers
