Clearing JRun 3.1 cache

[jdaniels]

I have a problem with running JRun 3.1 with Apache on a WinME machine:

When I make changes to a JSP file, the new file rarely gets displayed; instead an old version is used so this makes development a slow and painful process. Any way I can get the new JSP to be used as soon as it is changed? I have tried:

restarting Apache, Jrun and the whole machine
deleting servlets compiled out of the errant JSP
Renaming the file and using the new file

None of which works satisfactorily.

Thanks,

Jonathan Daniels

 

[pedrosolorzano]

Hi jdaniels:

I had the same problem, but with the IPlanet Web Server. The solution was a configuration parameter that disable the cache feature for development, so each time I reload a JSP the server compiles it. Once in production I set it true again. I can't help you now with JRun, but I'm sure that there is the same parameter to JRun, search about cache configurations in the JRun documentation.

Good Luck.

 

[jdaniels]

Actually I solved the problem. The JSP is called by a controller servlet and when calling the sendRedirect method in that servlet I hadn't included the port, which points me to a webserver.appserver coupling issue. Thanks anyway