Warning for Patch 7 - Updated

Question

I have just discovered that the caching
problems of "f60all.jar" are related to
its creation date and OAS. There is a bug
in OAS 4.0.8.1 that prevents files from
being cached if they were created after
February 29, 2000. To correct this problem
just apply the following patch to OAS :
http://metalink.oracle.com/metalink/plsql/dis_download.confirm?p_id=3660.999
Bug number is 1265536.
null

Answer 1

To see if Jinitiator is caching JAR files,
go to Jinitiator Control Panel, enable
the option "Show Java Console" and add to
"Java Run Time Parameters" the parameter :
... -Dcache.verbose=true
The message will be like this :
Opening http://www.company.com/jar/f60all.jar no proxy
Cache: http://www.company.com/jar/f60all.jar not modified since Tue Jan 25 10:30:16 GMT-02:00 2000
Cache: Cache hit for http://www.company.com/jar/f60all.jar
Another method is to check your WEB server.
You can activate XLF logging to register
all HTTP requests. In this log you can see
if a JAR file was downloaded (code 200) or
not (code 304).
null