• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Tomcat not recognizing changes!

 
Ranch Hand
Posts: 3695
IntelliJ IDE Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I know this has been discussed many times, both here and on the tomcat-user list. But today I'm running into this intermittent problem, and I'm very ... frustrated.

Tomcat 4.1.29
Apache 2.x
JK
Slackware 9

This has been running fine, with no problems, for a very long time. We'd make changes, save the JSP file, hit 'refresh' on our browser, and there would be our changes. No more.

Now, we can get away with making one change to a JSP page. If we save that and refresh, we see the change. On the second and any subsequent changes, the change is not recognized until we:
1) stop tomcat
2) clear the work directory
3) restart tomcat
4) hit 'refresh' on the browser.

Needless to say, this is a huge PITA during development. And we've made zero configuration changes between when it was "just working" and now, when it's clearly "not working".

I can confirm it's not client-side caching. I use IE for development. When I first ran into this situation, I switched to Mozilla (which I hadn't been running for about a week), and viewed the page. It also had the 'old' page. Aside from this, deleting cookies doesn't help.

It's not a network caching issue. There are no proxies between my machine and the server.

Again, there have been zero changes in any of the Apache/JK/Tomcat config files. This appears to have spontaneously stopped working properly.

Any ideas?
[ December 17, 2003: Message edited by: Mike Curwen ]
 
Sheriff
Posts: 7023
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
(Just a "me too".)
Since 4.1.27, I've noticed Tomcat acting similarly as you've described. I do seem to remember a day back around 4.1.24 when we didn't have these problems.
[ December 18, 2003: Message edited by: Dirk Schreckmann ]
 
Mike Curwen
Ranch Hand
Posts: 3695
IntelliJ IDE Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
hm... I was actually full of crap when i said 4.1.29.

We're running 4.1.24
 
Sheriff
Posts: 3341
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This happens a lot. Usually, the real issue is times on the server. If the times are off between you and the server, Tomcat doesn't see the new JSP file as newer than the compiled Java class. When this happens, if you "Touch" the jsp file on the server directly, Tomcat should then pick it up.
 
Mike Curwen
Ranch Hand
Posts: 3695
IntelliJ IDE Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Not in our case.

When we 'upload' our changed file, it gets time-stamped by the server. So our "modified" date is about 2 minutes in the past, according to my PC, but the server is the one doing the timestamp on the modified file, so it's internally consistent.
 
Mike Curwen
Ranch Hand
Posts: 3695
IntelliJ IDE Java Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Update.

Tried upgrading to TC 4.1.29. Same problem.

Synchronized the servers involved to within 1 second of each other. Same problem.

When our sysadmin took our box down on Christmas for some maintenance, when the box came back up, the problem corrected itself. So in our case, it seemed something in the OS was not happy (Slack9).
 
reply
    Bookmark Topic Watch Topic
  • New Topic