Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
JSP caching in websphere???
171 views
Skip to first unread message
Niclas Rothman
Sep 19, 2001, 8:51:22 AM9/19/01
to
Hi everyone
Im running Websphere advanced edition 3.5.4 and having serious problems.
When i update an implementation in an JSP file, the update has no impact. It
seems to be the case that websphere caches the file and doesn´t check if
there is a newer file that should be served. I´ve tried to delete the temp
directory in websphere containing the generated servlet and .dat files so
the files should be regenerated. This does not always solve my problem.
Any suggestion, information or fixes??
Im running Websphere advanced edition 3.5.4 and having serious problems.
When i update an implementation in an JSP file, the update has no impact. It
seems to be the case that websphere caches the file and doesn´t check if
there is a newer file that should be served. I´ve tried to delete the temp
directory in websphere containing the generated servlet and .dat files so
the files should be regenerated. This does not always solve my problem.
Any suggestion, information or fixes??
Best Regards
Niclas Rothman
n...@e-sense.dk
Alex Matthews
Sep 19, 2001, 9:46:54 AM9/19/01
to
There is a JSP caching facility in WAS, but by default it should be
disabled - check for messages that refer to a dynacache.xml file in your
log files. If enabled, dynamic content from specific JSPs will be cached
according to settings in this file.
disabled - check for messages that refer to a dynacache.xml file in your
log files. If enabled, dynamic content from specific JSPs will be cached
according to settings in this file.
If you change a JSP deleting the entry in the temp directory should
certainly have the effect you seem to be looking for.
Other than that, are you sure that the file is not being cached by your
browser or by an intermediate proxy server?
Alex.
Brian Cruess
Sep 19, 2001, 1:25:06 PM9/19/01
to
We found this same issue with JSP's and we don't have caching enabled as
well. If you are running Windows NT, then look under the TEMP directory in
the Appserver folder. You will see all of your applications on the server
with a folder. You can delete that folder and WAS will reload.
well. If you are running Windows NT, then look under the TEMP directory in
the Appserver folder. You will see all of your applications on the server
with a folder. You can delete that folder and WAS will reload.
What we have done when deploying JSP's or our Image files in WAS, we
automatically delete the application's folder under the TEMP folder before
restarting the application.
"Alex Matthews" <al...@xelacom.com> wrote in message
news:3BA8A1CE...@xelacom.com...
paul_...@uk.ibm.com
Sep 26, 2001, 11:39:40 AM9/26/01
to
One way to cause WebSphere to ignore JSP changes is to publish the new
source from a PC in an incorrect time zone. I had the opposite
experience, where my PC was configured as EST but was physically in the
UK. So files were published with a timestamp 5 hours in the future, and
every time WebSphere looked, its compiled code was out of date. If you
have the reverse problem (e.g. inconsistent clocks), you could get the
source published "in the past", and WebSphere would ignore the changes if
that time were before the most recent compilation.
source from a PC in an incorrect time zone. I had the opposite
experience, where my PC was configured as EST but was physically in the
UK. So files were published with a timestamp 5 hours in the future, and
every time WebSphere looked, its compiled code was out of date. If you
have the reverse problem (e.g. inconsistent clocks), you could get the
source published "in the past", and WebSphere would ignore the changes if
that time were before the most recent compilation.
Paul Gover
IBM Warwick Services Practice
Opinions my own, not IBM's
0 new messages