On Tue, Nov 5, 2019 at 3:01 AM Mark Thomas <ma...@apache.org> wrote: > This looks like some sort of concurrency issue. In your test > environment, how likely is it that: > - there are concurrent (or at least very close together) changes to a > JSP > - that there are concurrent requests for a modified JSP?
In my test env, I am the sole person making changes to the JSP. Also, in production, its only 1 single person making changes to a particular JSP. It is very likely that there are concurrent requests for the modified JSP. That is exactly how I am reproducing this, I basically have a curl command being executed every 0.5-1 seconds for that modified JSP when this intermittent issue occurs. With high production traffic, it's very possible that one or more users are hitting a modified JSP. > Also, what process are you using to update the JSP content? In my tests, I'm simply using VIM, in production, it's using a content management system which likely just copies the new JSP over, similar to an rsync or cp command. The issue is reproducible in both cases, as long as there are active requests for the modified JSP. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
