I'm using HttpClient for testing and when I have been restarting/redeploying to Tomcat I have been getting some sort of client side caching... For example I tried deleting my authentication servlet and ran my tester class (which connects using HttpClient) and I get the same response over and over. I'm going crazy trying to figure out what exactly is happening here.
Asked
Active
Viewed 871 times
2
-
1Which HttpClient class are you talking about? – Mike Baranczak Aug 07 '10 at 00:53
-
org.apache.http.client.HttpClient foo = new DefaultHttpClient(); – user398371 Aug 07 '10 at 02:32
-
Were you using HttpClient on the client-side or the server-side to call other services? I ran into a similar issue with HttpClient caching some information on the server-side. Can you provide more info? – Balaji Sep 15 '11 at 15:33
1 Answers
0
Please bear with me as I'm editing this on my mobile device.
In your META-INF/context.xml, add a PersistentManager with saveOnRestart set to false.
Example:
<Manager className="org.apache.catalina.session.PersistentManager" saveOnRestart="false">
<Store className="org.apache.catalina.session.FileStore" />
</Manager>
PS If this didn't help you, try this example here.
Community
- 1
- 1
Buhake Sindi
- 87,898
- 29
- 167
- 228
-
Hmm... I wasn't even using context.xml (I'm very new to this). This is the extent of what I did with no results after restarting the container/redploying.
-
No same place as before. I might try deploying it to a new copy of the container. – user398371 Aug 07 '10 at 00:32