You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by JS...@vinu.edu on 2003/10/17 20:54:38 UTC
RE: Server caching servlet response problem.
That's what I thought. You say that, but I don't see any errors. For
example, I have a servlet that's accessed by using
/Myapp/servlet/MyServlet. This works and shows the updated version every
time. As soon as the change is made you can refresh the browser and the
changes show up. But I also added a mapping to that same servlet using
/Myapp/map/*. When you access the servlet this way you get the first
response and from that time on you only get that response. If you change
the information it just keeps showing the last responses information. If
you then access the servlet using /Myapp/servlet/MyServlet it show the
changes. But the other mapping will never change it just keeps showing the
same response. I also get the same type of problem using jsp forwarding.
Can you tell me what I should start looking for? The logs don't show any
problems that I can see. Any suggestions?
Thank You,
Justin A. Stanczak
Web Manager
Shake Learning Resource Center
Vincennes University
(812)888-5813
"Shapira, Yoav" <Yo...@mpi.com>
10/17/2003 08:05 AM
Please respond to "Tomcat Users List"
To: "Tomcat Users List" <to...@jakarta.apache.org>
cc:
Subject: RE: Server caching servlet response problem.
Howdy,
Tomcat doesn't cache servlet responses. It's that simple.
The behavior you're seeing is most likely explained by an error in the
your servlet: check the server logs.
Yoav Shapira
Millennium ChemInformatics
>-----Original Message-----
>From: JStanczak@vinu.edu [mailto:JStanczak@vinu.edu]
>Sent: Thursday, October 16, 2003 7:54 PM
>To: tomcat-user@jakarta.apache.org
>Subject: Server caching servlet response problem.
>
>I'm running a Tomcat 5 on Solaris 9. For some reason the server keeps
>caching my responses. What happens is the first time I access my
servlet
>using a certain mapping the server caches that response and never
updates
>again. I have two instances of this. One is with a mapping to a servlet
>using this pattern /SoftwareName/servlet/site/* the other is when I
>forward from a jsp page to a servlet using the <jsp:forward> tag. Both
of
>these methods cache the first response and that's what's send for every
>response. Even if I go to a completely different computer that's never
>access before. Can someone tell me what's wrong. This can't be correct
>behavior.
>
>
>Thank You,
>
>Justin A. Stanczak
>Web Manager
>Shake Learning Resource Center
>Vincennes University
>(812)888-5813
This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential,
proprietary and/or privileged. This e-mail is intended only for the
individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your
computer system and notify the sender. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
RE: Server caching servlet response problem.
Posted by Wade Chandler <wc...@redesetgrow.com>.
Are you catching Exceptions? If so are you doing anything with them, or
are you swallowing them?
Wade
-----Original Message-----
From: JStanczak@vinu.edu [mailto:JStanczak@vinu.edu]
Sent: Friday, October 17, 2003 2:55 PM
To: Tomcat Users List
Subject: RE: Server caching servlet response problem.
That's what I thought. You say that, but I don't see any errors. For
example, I have a servlet that's accessed by using
/Myapp/servlet/MyServlet. This works and shows the updated version every
time. As soon as the change is made you can refresh the browser and the
changes show up. But I also added a mapping to that same servlet using
/Myapp/map/*. When you access the servlet this way you get the first
response and from that time on you only get that response. If you change
the information it just keeps showing the last responses information. If
you then access the servlet using /Myapp/servlet/MyServlet it show the
changes. But the other mapping will never change it just keeps showing
the
same response. I also get the same type of problem using jsp forwarding.
Can you tell me what I should start looking for? The logs don't show any
problems that I can see. Any suggestions?
Thank You,
Justin A. Stanczak
Web Manager
Shake Learning Resource Center
Vincennes University
(812)888-5813
"Shapira, Yoav" <Yo...@mpi.com>
10/17/2003 08:05 AM
Please respond to "Tomcat Users List"
To: "Tomcat Users List" <to...@jakarta.apache.org>
cc:
Subject: RE: Server caching servlet response problem.
Howdy,
Tomcat doesn't cache servlet responses. It's that simple.
The behavior you're seeing is most likely explained by an error in the
your servlet: check the server logs.
Yoav Shapira
Millennium ChemInformatics
>-----Original Message-----
>From: JStanczak@vinu.edu [mailto:JStanczak@vinu.edu]
>Sent: Thursday, October 16, 2003 7:54 PM
>To: tomcat-user@jakarta.apache.org
>Subject: Server caching servlet response problem.
>
>I'm running a Tomcat 5 on Solaris 9. For some reason the server keeps
>caching my responses. What happens is the first time I access my
servlet
>using a certain mapping the server caches that response and never
updates
>again. I have two instances of this. One is with a mapping to a servlet
>using this pattern /SoftwareName/servlet/site/* the other is when I
>forward from a jsp page to a servlet using the <jsp:forward> tag. Both
of
>these methods cache the first response and that's what's send for every
>response. Even if I go to a completely different computer that's never
>access before. Can someone tell me what's wrong. This can't be correct
>behavior.
>
>
>Thank You,
>
>Justin A. Stanczak
>Web Manager
>Shake Learning Resource Center
>Vincennes University
>(812)888-5813
This e-mail, including any attachments, is a confidential business
communication, and may contain information that is confidential,
proprietary and/or privileged. This e-mail is intended only for the
individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else. If you are not the(an)
intended recipient, please immediately delete this e-mail from your
computer system and notify the sender. Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org