Frank Schubert

Disable JSP Compiler Cache in 7.2

Discussion created by Frank Schubert on Apr 9, 2020
Latest reply on Aug 17, 2020 by Ian Staines

Hi all,

 

the ones who develop JSPs may battle with this already: once you change a JSP and upload it, the new version doesn't become active until after the next aveksa_server restart. Alternatively, as discussed in @JSP Validation in 7.2 you could version your JSPs.

Both have disadvantages. The former takes ages and I don't want spent valuable time waiting for this thing to come back and the latter creates tons of file that I may need to clean up one-by-one and I may need to change config here and there to adjust to the new file name.

 

The quickest way I found out is to disable the compiler cache altogether. On development systems this is totally doable, low risk and can be rolled-back easily.

 

  1. find your
    aveksa-standalone-full.xml
    (standard install in
    /home/oracle/wildfly/standalone/configuration
    )
  2. edit it and fine the line
    <jsp-config/> 
    and change it to
  3. <jsp-config development="true" check-interval="1" modification-test-interval="1" recompile-on-fail="true"/>
  4. Save the file and restart the server
  5. done

 

Hope this helps

 

Frank

Outcomes