Re: Tomcat intermittent failures

[David Bank]

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 you describe, because we only have 2-3 people at present hitting
the box at the same time.

David Bank
NC CATS Project Manager
Accountability Services - Testing
NC Department of Public Instruction
301  Wilmington Street
Raleigh, NC  27601
919-807-3796

>>> [EMAIL PROTECTED] 04/10/02 02:07AM >>>
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
(before moving to a QA box).

What I don't know off the top of my head, is whether it is possible a
setting exists in Win2K server to control the number of connections to
allow. Just thought this info might give someone else, or you, an idea
or
two.

Hope it helps.

Joe

- Original Message -
From: "David Bank" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 09, 2002 10:55 AM
Subject: Tomcat intermittent failures


> Good morning, afternoon, evening, or whichever local timeperiod you
are
> currently experiencing. I've just joined the list, seeking help on a
> rather perplexing Tomcat problem we've been having. All assistance
will
> be greatly appreciated.
>
> Our environment
> Windows 2000 Server (sorry) with SP2 (we're moving to Linux, I
> promise!)
> Apache v1.3.23
> Tomcat v3.3a (running as a NT service)
> Sun JDK 1.3.1_02
>
> Our problem
> Occasionally, especially after editing a JSP file or files, Tomcat
will
> suddenly fail to find the .java and .class files that go with a
> particular JSP. Looking in the "work" directory reveals that the
files
> exist, but when we attempt to access that particular JSP thru Apache,
we
> get 404 - File Not Found.
>
> We have had some success in causing this problem to go away by
shutting
> down the Apache and Tomcat services, deleting the appropriate .java
and
> .class (and .ver) files, restarting the Tomcat and Apache services,
and
> hitting Reload on the browser. Sometimes (about 50% of the time) when
we
> do this, Tomcat suddenly "finds" the files and the JSP runs, new
.java
> and .class files are created, and we get the proper output. The
> remaining 50% of the time, it falls to one of two happenstances.
Either
> (30%) we do the shutdown-services-and-delete routine followed by a
> reboot and the problem goes away, or (20%) we keep retrying on
different
> clients until the problem suddenly vanishes.
>
> This problem is intermittent. Sometimes we'll get it with FOO.JSP
but
> not BAR.JSP. We'll then take a corrective action (described above)
and
> suddenly we'll get it with BAR.JSP but not FOO.JSP. Both JSP files
are
> very similar, and there's nothing exotic about our coding. Sometimes
the
> problem goes away with some waiting.
>
> This happens with both IE and Netscape clients, and with clients on
> different networks and behind different firewall/proxy situations, so
we
> don't think that firewall, proxy or other network architecture
issues
> are contributing factors. This happens to clients on the same LAN as
the
> servers.
>
> Needless to say, we're quite perplexed, and don't understand what is
> going wrong. If anyone has any suggestions or recommendations,
please
> respond.
>
> David Bank
> NC CATS Project Manager
> Accountability Services - Testing
> NC Department of Public Instruction
> 301  Wilmington Street
> Raleigh, NC  27601
> 919-807-3796
>
>
> --
> To unsubscribe:  

> For additional commands:

> Troubles with the list:

>
>

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

Re: Tomcat intermittent failures

[Joseph Molnar]

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
(before moving to a QA box).

What I don't know off the top of my head, is whether it is possible a
setting exists in Win2K server to control the number of connections to
allow. Just thought this info might give someone else, or you, an idea or
two.

Hope it helps.

Joe

- Original Message -
From: "David Bank" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 09, 2002 10:55 AM
Subject: Tomcat intermittent failures


> Good morning, afternoon, evening, or whichever local timeperiod you are
> currently experiencing. I've just joined the list, seeking help on a
> rather perplexing Tomcat problem we've been having. All assistance will
> be greatly appreciated.
>
> Our environment
> Windows 2000 Server (sorry) with SP2 (we're moving to Linux, I
> promise!)
> Apache v1.3.23
> Tomcat v3.3a (running as a NT service)
> Sun JDK 1.3.1_02
>
> Our problem
> Occasionally, especially after editing a JSP file or files, Tomcat will
> suddenly fail to find the .java and .class files that go with a
> particular JSP. Looking in the "work" directory reveals that the files
> exist, but when we attempt to access that particular JSP thru Apache, we
> get 404 - File Not Found.
>
> We have had some success in causing this problem to go away by shutting
> down the Apache and Tomcat services, deleting the appropriate .java and
> .class (and .ver) files, restarting the Tomcat and Apache services, and
> hitting Reload on the browser. Sometimes (about 50% of the time) when we
> do this, Tomcat suddenly "finds" the files and the JSP runs, new .java
> and .class files are created, and we get the proper output. The
> remaining 50% of the time, it falls to one of two happenstances. Either
> (30%) we do the shutdown-services-and-delete routine followed by a
> reboot and the problem goes away, or (20%) we keep retrying on different
> clients until the problem suddenly vanishes.
>
> This problem is intermittent. Sometimes we'll get it with FOO.JSP but
> not BAR.JSP. We'll then take a corrective action (described above) and
> suddenly we'll get it with BAR.JSP but not FOO.JSP. Both JSP files are
> very similar, and there's nothing exotic about our coding. Sometimes the
> problem goes away with some waiting.
>
> This happens with both IE and Netscape clients, and with clients on
> different networks and behind different firewall/proxy situations, so we
> don't think that firewall, proxy or other network architecture issues
> are contributing factors. This happens to clients on the same LAN as the
> servers.
>
> Needless to say, we're quite perplexed, and don't understand what is
> going wrong. If anyone has any suggestions or recommendations, please
> respond.
>
> David Bank
> NC CATS Project Manager
> Accountability Services - Testing
> NC Department of Public Instruction
> 301  Wilmington Street
> Raleigh, NC  27601
> 919-807-3796
>
>
> --
> To unsubscribe:   
> For additional commands: 
> Troubles with the list: 
>
>

--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

RE: Tomcat intermittent failures

[David Bank]

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 happening.

Thanks again for helping.

David Bank
NC CATS Project Manager
NC Department of Public Instruction
301  Wilmington StrDavid Bank
NC CATS Project Manager
Accountability Services - Testing
NC Department of Publeet
Raleigh, NC  27601
919-807-3796

>>> [EMAIL PROTECTED] 04/09/02 02:06PM >>>
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 PROTECTED]] 
> Sent: Tuesday, April 09, 2002 1:56 PM
> To: [EMAIL PROTECTED] 
> Subject: Tomcat intermittent failures
> 
> 
> Good morning, afternoon, evening, or whichever local 
> timeperiod you are
> currently experiencing. I've just joined the list, seeking help on a
> rather perplexing Tomcat problem we've been having. All 
> assistance will
> be greatly appreciated.
> 
> Our environment
> Windows 2000 Server (sorry) with SP2 (we're moving to Linux, I
> promise!)
> Apache v1.3.23
> Tomcat v3.3a (running as a NT service)
> Sun JDK 1.3.1_02
> 
> Our problem
> Occasionally, especially after editing a JSP file or files, 
> Tomcat will
> suddenly fail to find the .java and .class files that go with a
> particular JSP. Looking in the "work" directory reveals that the
files
> exist, but when we attempt to access that particular JSP thru 
> Apache, we
> get 404 - File Not Found. 
> 
> We have had some success in causing this problem to go away 
> by shutting
> down the Apache and Tomcat services, deleting the appropriate 
> .java and
> .class (and .ver) files, restarting the Tomcat and Apache 
> services, and
> hitting Reload on the browser. Sometimes (about 50% of the 
> time) when we
> do this, Tomcat suddenly "finds" the files and the JSP runs, new
.java
> and .class files are created, and we get the proper output. The
> remaining 50% of the time, it falls to one of two 
> happenstances. Either
> (30%) we do the shutdown-services-and-delete routine followed by a
> reboot and the problem goes away, or (20%) we keep retrying 
> on different
> clients until the problem suddenly vanishes.
> 
> This problem is intermittent. Sometimes we'll get it with FOO.JSP
but
> not BAR.JSP. We'll then take a corrective action (described above)
and
> suddenly we'll get it with BAR.JSP but not FOO.JSP. Both JSP files
are
> very similar, and there's nothing exotic about our coding. 
> Sometimes the
> problem goes away with some waiting.
> 
> This happens with both IE and Netscape clients, and with clients on
> different networks and behind different firewall/proxy 
> situations, so we
> don't think that firewall, proxy or other network architecture
issues
> are contributing factors. This happens to clients on the same 
> LAN as the
> servers.
> 
> Needless to say, we're quite perplexed, and don't understand what is
> going wrong. If anyone has any suggestions or recommendations,
please
> respond.


--
To unsubscribe:   
For additional commands: 
Troubles with the list: 

RE: Tomcat intermittent failures

[Larry Isaacs]

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 PROTECTED]] 
> Sent: Tuesday, April 09, 2002 1:56 PM
> To: [EMAIL PROTECTED]
> Subject: Tomcat intermittent failures
> 
> 
> Good morning, afternoon, evening, or whichever local 
> timeperiod you are
> currently experiencing. I've just joined the list, seeking help on a
> rather perplexing Tomcat problem we've been having. All 
> assistance will
> be greatly appreciated.
> 
> Our environment
> Windows 2000 Server (sorry) with SP2 (we're moving to Linux, I
> promise!)
> Apache v1.3.23
> Tomcat v3.3a (running as a NT service)
> Sun JDK 1.3.1_02
> 
> Our problem
> Occasionally, especially after editing a JSP file or files, 
> Tomcat will
> suddenly fail to find the .java and .class files that go with a
> particular JSP. Looking in the "work" directory reveals that the files
> exist, but when we attempt to access that particular JSP thru 
> Apache, we
> get 404 - File Not Found. 
> 
> We have had some success in causing this problem to go away 
> by shutting
> down the Apache and Tomcat services, deleting the appropriate 
> .java and
> .class (and .ver) files, restarting the Tomcat and Apache 
> services, and
> hitting Reload on the browser. Sometimes (about 50% of the 
> time) when we
> do this, Tomcat suddenly "finds" the files and the JSP runs, new .java
> and .class files are created, and we get the proper output. The
> remaining 50% of the time, it falls to one of two 
> happenstances. Either
> (30%) we do the shutdown-services-and-delete routine followed by a
> reboot and the problem goes away, or (20%) we keep retrying 
> on different
> clients until the problem suddenly vanishes.
> 
> This problem is intermittent. Sometimes we'll get it with FOO.JSP but
> not BAR.JSP. We'll then take a corrective action (described above) and
> suddenly we'll get it with BAR.JSP but not FOO.JSP. Both JSP files are
> very similar, and there's nothing exotic about our coding. 
> Sometimes the
> problem goes away with some waiting.
> 
> This happens with both IE and Netscape clients, and with clients on
> different networks and behind different firewall/proxy 
> situations, so we
> don't think that firewall, proxy or other network architecture issues
> are contributing factors. This happens to clients on the same 
> LAN as the
> servers.
> 
> Needless to say, we're quite perplexed, and don't understand what is
> going wrong. If anyone has any suggestions or recommendations, please
> respond.
> 
> David Bank
> NC CATS Project Manager
> Accountability Services - Testing
> NC Department of Public Instruction
> 301  Wilmington Street
> Raleigh, NC  27601
> 919-807-3796
> 
> 
> --
> To unsubscribe:   
> For additional commands: 
> Troubles with the list: 
> 

--
To unsubscribe:   
For additional commands: 
Troubles with the list: