• Post Reply Bookmark Topic Watch Topic
  • New Topic

JSPs not recompiling on new deployments  RSS feed

 
Ryan Kade
Ranch Hand
Posts: 69
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello everyone,

JBoss seems to still have a problem knowning when to recompile JSPs on new deployments. Whenever I deploy an EAR that has JSPs with an earlier compile date (say, for example, when I'm doing a rollback to a previous version out of version control), JBoss does not recompile them, and thus the "old" (but newer time-stamped) JSPs stay active.

The only way to avoid this is to (1) "touch" all the JSPs each time we do a build (even when reverting to an old build out of VC), (2) delete the /work directory manually, or (3) do a restart after each deploy. None of these is desirable, particularly when dealing with a production environment.

It's actually a Tomcat issue that has been logged in their bug-tracking system (bug #33453) and also in JBoss's JIRA (#JBAS-3081). The Tomcat folks appear not to want to integrate a fix, and the solution instead was to have JBoss (or Tomcat) actually delete the /work directory automatically after each deploy.

This would work for us, and was supposed to be available in 4.0.4. We're running 4.0.5.GA and I can confirm the /work directory is NOT being deleted. I even downloaded a fresh JBoss install and pushed a dummy WAR just to test it.

Is anyone else seeing this problem? Thanks!

Ryan
[ August 17, 2007: Message edited by: Ryan Kade ]
 
ray livia
Greenhorn
Posts: 16
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I and using the 4.0.5GA version and encounter this problem in my live env. Does anyone know which version could fix this issue? We have to clean the work folder manually!
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!