Cache-Control: no-cache

I have Web Cache set up with an Apache Server and it is returning requests from the cache. I have a response monitoring tool that sends the HTTP 1.1 Cache-Control: no-cache header on the request but Web Cache still returns from cache rather than getting the page from the server. The only configuration option appears to control honoring of response headers not request headers. Shouldn't Web Cache always honor request headers?

Hi,
Yes, it should and will, as far as I have seen, honor request headers too. But, AFAIK, "Cache-Control: no-cache" is a reposne header (as given in HTTP RFC):
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.1
So, specifying this in the request doesn't have effect.
Hope this helps.
Regards,
Priyanka
Oracle Web Cache Team

Similar Messages

JRE Cache ignores the "Expire" and "Cache-Control: no-cache" directives.

My applet is using HttpURLConection to retrieve data from a server with Caching enabled. The cache contents are "revalidated" (via "if-modfied-since") each time the applet is started. However, subsequent requests to retrieve the same resource are always read from the cache with no validation even if the resource has expired.
The server is sending a valid "Expires:" tag and "Cache-Control: no-cache" tag in the response; but, the JRE refuses to recheck for an updated version of the resource even after the file has expired.
The JRE does seem to understand the "Cache-Control: no-store" tag; but, this is inefficient (no caching at all) when I'm tring to get it to not refetch the resource unless there's a change. Is there some other tag that the JRE is expecting to see?

I have a similar problem except that I want my pages to not cache at all. The server is setting the Cache-Control: max-age to 0 and the Expires to "now" but JRE seems to ignore these settings, but only sometimes. Sometimes pages are fetched from cache and sometimes from the server.
In my applet I'm using a normal URLConnection like this:
URLConnection uc = new URL("http://<server>/method").openConnection();
uc.connect();
InputStream is = uc.getInputStream();
is.read();When my request headers look like this:
accept-encoding: gzip
Host: <server>
Cache-Control: no-cache
Pragma: no-cache
User-Agent: Mozilla/4.0 (Windows XP 5.1) Java/1.6.0_13
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-alivethe page will not be cached and is requested again but this time without the accept-encoding, Pragma and Cache-Control. The adding (and removal) of the headers seems to happen inside the JRE, though. I'm not explicitly setting them.
The response header of the first request looks like this:
HTTP/1.1 200 OK
Date: Wed, 20 May 2009 12:55:07 GMT
Server: Apache/2.2.11 (Win32) mod_jk/1.2.26 PHP/5.2.8
Cache-Control: max-age=0
Expires: Wed, 20 May 2009 12:55:07 GMT
Vary: User-Agent,Accept-Encoding
Content-Encoding: gzip
Keep-Alive: timeout=120, max=79
Connection: Keep-Alive
Transfer-Encoding: chunked
Content-Type: text/html;charset=iso-8859-1When the request is made with this header:
User-Agent: Mozilla/4.0 (Windows XP 5.1) Java/1.6.0_13
Host: <server>
Accept: text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2
Connection: keep-aliveThe response headers looks like this:
HTTP/1.1 200 OK
Date: Wed, 20 May 2009 12:55:07 GMT
Server: Apache/2.2.11 (Win32) mod_jk/1.2.26 PHP/5.2.8
Content-Length: 1016
Cache-Control: max-age=0
Expires: Wed, 20 May 2009 12:55:07 GMT
Vary: User-Agent,Accept-Encoding
Keep-Alive: timeout=120, max=83
Connection: Keep-Alive
Content-Type: text/html;charset=iso-8859-1And in this case the JRE sometimes fetches the request from the server and sometimes from cache. I have not been able to determine how the JRE decides to refresh, or why it sometimes sends an accept-encoding and Pragma header and sometimes not.
any help would be appreciated.
Alex

"Content-type: text/html; charset=utf-8 cache-control: no-cache..." display

"Content-type: text/html; charset=utf-8 cache-control: no-cache, no-store, max-age=0, must-revalidate pragma: no-cache X-Frame-Options: DENY "
is being displayed at the top of one of our pages now. I can see that line in the body section of the page using Firebug, but can't find what is creating it there.
Does anyone have any tips on how I would go about finding something like this?
The page was using a custom theme but that stopped working when we upgraded to 4.1. So, I copied the Simple Green template to start modifying.
Mentioning that in case it's relevant...
Thanks!

LauraC wrote:
"Content-type: text/html; charset=utf-8 cache-control: no-cache, no-store, max-age=0, must-revalidate pragma: no-cache X-Frame-Options: DENY "Looks like an HTTP header...
is being displayed at the top of one of our pages now. I can see that line in the body section of the page using Firebug, but can't find what is creating it there.
Does anyone have any tips on how I would go about finding something like this?If it's included within the <tt>body</tt> element in the original page source then it's produced by something in APEX and the position in the source will give a clue as to where. You should also run the page in Debug mode and look at the trace to see if there's any clues there.
If it's visible in the generated page source but not the original then it's produced by something dynamic in the page. Possibly some JS lingering from the previous theme?

Weblogic setting Cache-control: no-cache?

I have a servlet filter that sets the Cache-control http header to "max-age=30" for static files such as *.css but in the end weblogic sends the value "no-cache".
When the browser asks for the same static file again weblogic responds with http 304 and Cache-control "max-age=0" thus overriding my filter again.
Is there any way to change the client side caching in weblogic (10.3.4)?
(btw the servlet filter works in tomcat)

Hi,
1. response.setHeader("Cache-Control","no-cache");
This is used to prevent the browser from caching your dynamic content generated by a JSP or Servlet.
You set this attribute in the HTTP header of the response object which would tell the browser not to cache this content. So everytime you request the page again, the browser would make a new request, instead of showing you a cached page.
2. response.setHeader("Location", "error.html");
This is called redirecting. "Redirecting" is sending a response from your servlet to the browser telling the browser to go to a new location(make a new request)
The standard way to do this response.sendRedirect(String);

Selective Cache-control in the web server

I am using weblogic 8.1 as the app server and Sun one 6.1 as the web server
In my obj.conf of the web server we have this
PathCheck fn="set-cache-control" control="private"
This caches all the pages.
But I don't want some pages to be cached in our site.
For this, I tried setting "no-cache" for the "Cache-control " of the response hedear, in corresponding jsps. But the webserver configuration is overriding this.
This configuration set in the webserver should be applicable for all the modules except for some urls .
can anybody tell me how to make this selective cache-control configuration in the obj.conf of sun one web server.
or if there is any way to prevent the set up in jsp from being overridden this webserver ?
Also it would be great if anybody can explain, what are the services handled by the web server and the the app-server and how they interact with each other....

It's unfortunate that JSPs running in WebLogic can't override the default Cache-Control directives in Web Server. That's probably a bug in the WebLogic plugin. (It is possible for JSPs running directly on Web Server to override the default Cache-Control directives.)
As with any obj.conf directive, you can configure Cache-Control directives on a path-by-path basis. For example, the following would set Cache-Control: no-cache for /foo/*.jsp and Cache-Control: private for all other URIs:<Object ppath="/foo/*.jsp">
PathCheck fn="set-cache-control" control="no-cache"
</Object>
<Object name="default">
PathCheck fn="set-cache-control" control="private"
</Object>Information on obj.conf syntax, including how to configure separate objects for separate paths, can be found in the Syntax and use of obj.conf chapter of the NSAPI Programmer's Guide at http://docs.sun.com/source/817-6252/npgobjcn.html.
I'm not sure what you mean by "what are the services handled by the web server and the the app-server and how they interact with each other". However, it's worth noting that Sun ONE Web Server 6.1 is fully capable of running JSPs by itself; there's no need for a separate WebLogic server.

Controlling Cache-Control headers

We have an application written in BC4J 9.0.3.4 riding atop 9iAS 9.0.3.1.0.
The release notes for this version of 9iAS say
2484551 Microsoft Internet Explorer cannot open some file directories due to HTTP NO-STORE header
If users use Microsoft Internet Explorer 6.0.2600.0000, then they cannot open some attachments, such as Microsoft PowerPoint or voicemail directly. They have to save the file and open it from their file system. The file cannot be opened because Microsoft Internet Explorer 6.0 doesn't save the file to the <code>temp</code> folder when an HTTP no-store header is set.
Saying that this is fixed is, to say the least, iffy. A packet dump clearly shows the following headers being set at some point after JSP filters get a chance to kick in (i.e., probably by mod_oc4j itself):
Pragma: no-cache
Cache-Control: no-store
Surrogate-Control: no-store
Cache-Control: private
There doesn't seem to be any way of turning these headers off other than using .htaccess and mod_headers to explicitly delete them (which is definitely not ideal). Further, my tests indicate that these headers (probably only Cache-Control: no-store) prevent IE5.5 and IE6 both from launching external applications on the basis of Content-Type / extension, and from saving the page at all.
This is, admittedly, a violation of RFC2616 on IE's part: that RFC states that no-store is meant to apply to intermediate proxies, not to user agents themselves. But nonetheless I think Oracle should at least allow pandering to this particular bug; i.e., even if Cache-Control: no-store is on by default, it should be possible to turn it off.
Am I missing something? Is there any way to stop mod_oc4j adding these headers?

I tried the brute-force approach:
Header set Cache-Control: no-cache
Header set Surrogate-Control: no-cache
in .htaccess.
Alas, .htaccess isn't being read, even with
<Directory /oracle/product/ias_903/j2ee/OC4J_DEV/applications>
AllowOverride FileInfo
</Directory>
in the httpd.conf.
This is confusing. Does mod_oc4j somehow ban the processing of .htaccess files even if the AllowOverride says otherwise?

Cache control in wml

hi,
I am getting problem in cache controlling in wml page for example a image displayed on the page is not displaying again but i am getting same in the console..help me out....

It's unfortunate that JSPs running in WebLogic can't override the default Cache-Control directives in Web Server. That's probably a bug in the WebLogic plugin. (It is possible for JSPs running directly on Web Server to override the default Cache-Control directives.)
As with any obj.conf directive, you can configure Cache-Control directives on a path-by-path basis. For example, the following would set Cache-Control: no-cache for /foo/*.jsp and Cache-Control: private for all other URIs:<Object ppath="/foo/*.jsp">
PathCheck fn="set-cache-control" control="no-cache"
</Object>
<Object name="default">
PathCheck fn="set-cache-control" control="private"
</Object>Information on obj.conf syntax, including how to configure separate objects for separate paths, can be found in the Syntax and use of obj.conf chapter of the NSAPI Programmer's Guide at http://docs.sun.com/source/817-6252/npgobjcn.html.
I'm not sure what you mean by "what are the services handled by the web server and the the app-server and how they interact with each other". However, it's worth noting that Sun ONE Web Server 6.1 is fully capable of running JSPs by itself; there's no need for a separate WebLogic server.

Cache-Control in OC4J

We had very typical problem in our web application.
We are using Oracle AppServer 10.1.2. on Sun Solaris with Web-Cache Enabled.
When we are trying to access the pages the response object contains multiple Cache-Control headers, though we have not explicitly added through our code. Can any one tell me how to delete the response headers through code or at server settings. I have tried with "reset()" but of no use.
Because of this cache problem we are not able to generate the reports but the same it working with Firefox browser.
Thanks in advance.
Kishore

It's unfortunate that JSPs running in WebLogic can't override the default Cache-Control directives in Web Server. That's probably a bug in the WebLogic plugin. (It is possible for JSPs running directly on Web Server to override the default Cache-Control directives.)
As with any obj.conf directive, you can configure Cache-Control directives on a path-by-path basis. For example, the following would set Cache-Control: no-cache for /foo/*.jsp and Cache-Control: private for all other URIs:<Object ppath="/foo/*.jsp">
PathCheck fn="set-cache-control" control="no-cache"
</Object>
<Object name="default">
PathCheck fn="set-cache-control" control="private"
</Object>Information on obj.conf syntax, including how to configure separate objects for separate paths, can be found in the Syntax and use of obj.conf chapter of the NSAPI Programmer's Guide at http://docs.sun.com/source/817-6252/npgobjcn.html.
I'm not sure what you mean by "what are the services handled by the web server and the the app-server and how they interact with each other". However, it's worth noting that Sun ONE Web Server 6.1 is fully capable of running JSPs by itself; there's no need for a separate WebLogic server.

Cache-Control problem

I don't really know if this is a Tomcat problem or a jsp problem... I have some java server pages with form components and when I hit the back button in a browser, the contents of a form disappear. I checked the response header with a perl script and it seems that there's always Cache-Control: no-cache and Pragma: No-cache in the header. I didn't put them there. I've tried to put some lines as
response.setHeader("Cache-Control","max-age=3600");
response.setHeader("Pragma","max-age=3600");
response.addHeader("Cache-Control","max-age=3600");
response.addHeader("Pragma","max-age=3600");
into my jsp, but they have no effect. I've tried disabling all filters, no effect. I've done a full text search on the whole tomcat directory tree with keywords like no-cache, cache-control and those words don't appear anywhere (but in my jsp). I suspected that apache could mess things up, but browsing the jsp's directly from tomcat (through port 8080) does the same.
Running out of ideas... Do you have any?
-Marko

It's neither. It's a browser problem... and perhaps your assumption that the browser has to remember what was in the form fields when you go back. Cache control has to do with caching the page, not form input anyway. I've never seen any header settings which tell instruct a browser what to do with form data after the form is submitted.
You could provide a back button on the form and have the JSP fill in the default values based on what's stored in the session, if you are storing it in the session. But if it's not a multipage form, there usually is no reason to be "going back" anyway, because the form is submitted and whatever's done with that data should be done by that point.
Tomcat could be defining default headers for anything in some config file.

Cache-control header

I have an authenticated webapp with a servlet that send information back to the client browser that is not particularly sensitive. As such, I'd like for the client to be able to cache the retrieved data for a reasonable amount of time.
Thus, I've added the following code to my servlet:
long expireTime = System.currentTimeMillis() + (7 * 24 * 3600 * 1000); // Cache for one week
response.setDateHeader("Expires", expireTime);
response.setHeader("Pragma", "cache");
response.setHeader("Cache-control", "public");While my expires header is indeed getting set to the date that I specify, AS7 is ignoring my Pragma header and sending two (!) Cache-control headers (as seen in a packet dump using ethereal):
Hypertext Transfer Protocol
    HTTP/1.1 200 OK\r\n
    Server: Sun-Java-System-Application-Server/7 2004Q2\r\n
    Date: Sat, 23 Apr 2005 01:30:15 GMT\r\n
    Content-type: message/rfc822\r\n
    Expires: Sat, 30 Apr 2005 01:30:15 GMT\r\n
    Pragma: No-cache\r\n
    Content-disposition: attachment;filename=msg145206-11461.eml\r\n
    Cache-control: no-cache\r\n
    Cache-control: public\r\n
    Transfer-Encoding: chunked\r\n
    \r\n
    HTTP chunked responseAm I doing something wrong, or is this a bug in AS7?
This is really causing a problem, because I want the browser to toss this data stream over to Outlook Express (the data is an e-mail message) but IE sees the no-cache header and refuses to write the file to disk, and thus, OE has no file to open.
Thanks,
Bill

Oh, BTW we believe this header modification is happening because we are setting a cookie and so WLS sees this and adds its own header. Still, we don't want WLS to do anything with the headers.

Control client cache for JSP

There are many threads on the web about how to force a reload rather than pulling content from cache. My problem is the opposite. I am trying to get good cache control for a jsp application that has relatively static contents. My goal is to serve up pages with the following characteristics:
For client calls:
If there is no version in cache, the jsp builds a new version and sets the response date header "Expires" to 5 days later.
If within the Expires date, have the client just use the cached version: no validation or roundtripping.
If after the Expires date, roundtrip: have the jsp return 303 (SC_NOT_MODIFIED) if no content changed. Also, ideally, also reset the Exipres date to an additional 5 days.
Otherwise, recreate the response and start over...
I am experiencing different behaviors with different browsers, although none act as I was hoping.
When there is no relevant page in cache, all of the browsers accept a new version (and I think that they all put it in cache). All browsers reload the page using the reload button.
If there is a relevant page in cache and it has not expired:
1. FireFox 3 seems to roundtrip, but then use the version in cache.
2. IE 7 seems to always use the cache version without checking the server
3. Google Chrome seems to always roundtrip and reload.
I tried several variations including setting/not setting the Last-Modified date header and setting/not Cache-Control: no-control header (to force validation).
Neither Last-Modified nor no-contro: NO CHANGE FROM ABOVE;
Last-Modified set, no-control not specified: NO CHANGE
Last-Modified not set, Cache-Control set to no-control to force validation.
The main problem here is that I was unable to get a value for the request header "Last-Modifier" so that my jsp could not set the 303 return, therefore all browsers roundtrip and reload.
SO...
1. What do I need to do to get all browsers to pull from cache and not roundtrip prior to the Expires date?
2. After the Expires date, what do I need to do to get the request to include the Last-Modified date header sent to the server?
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><%
%><%@ page import="java.net.*"%><%
%><%@ page import="java.util.*"%><%
%><%@ page import="java.util.Date"%><%
%><%@ page import="javax.servlet.*"%><%
%><%@ page import="java.text.SimpleDateFormat" %><%
// In a real application, the updatedDate would come from a database or file
Calendar thisCal = new GregorianCalendar();
thisCal.set(2009,02,15);
Date     updateDate = thisCal.getTime();
// This never returns a valid date
long thisLongDate = request.getDateHeader("Last-Modified");
Date cachedDate    = ((thisLongDate<0)?null:new Date(thisLongDate));
Date todaysDate    = new Date();
// Show all three dates in the output
String   outString = "";
SimpleDateFormat   showDateFormatter = new SimpleDateFormat ("yyyy-MM-dd hh:mm:ss");
outString += "================================================================<br> \n";
outString += " Start TestSuite25.jsp "+showDateFormatter.format(todaysDate)+"<br> \n";
outString += "Update date is "+showDateFormatter.format(updateDate)+"<br> \n";
outString += "Cached date is "+((cachedDate==null)?null:showDateFormatter.format(cachedDate))+"<br> \n";
response.setContentType("text/html");
if (request.getParameter("lastmodified") != null)
   outString += "Set Last Modified header: may trigger If-Modified-Since request. <br> \n";
   response.setDateHeader("Last-Modified",updateDate.getTime());
// force validation .. does this hit my code??
if (request.getParameter("cache") != null)
    outString += "Set cache control to no-cache to force validation on every call<br> \n";
    response.setHeader("Cache-Control", "no-cache");
// use cache for 5 days, then validate
thisCal.setTime(todaysDate);
thisCal.add(Calendar.DATE,5);
response.setDateHeader("Expires", thisCal.getTime().getTime());
// Check for still fresh on server
if (!(cachedDate == null) && (!cachedDate.before(updateDate)))
   outString += "Contents are unchanged: send 303 status message<br> \n";
   response.setStatus(HttpServletResponse.SC_NOT_MODIFIED);
   System.out.println(outString);
else
   outString += "Rebuild and send the HTML <br>";
   System.out.println(outString);
   // Build and send the HTML ...
%>
<html>
<head>
<title>Test suite</title>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body >
<br>
<h2 align="center">Test 25: Controlling Cache</h2>
<h3 align="center">Click <a href="TestSuite21.html">here</a> to continue to Test 26.</h3>
useage: TestSuite25.jsp<br>
optional parameters: <br>
   cache=nocache: include no-cache to force validation each time<br>
   lastmodify=set: include Last-Modified date hearer<br>
<br>
<%=outString%>
</html>
</body>
<% } %>

let me tell you from BSP side !
within your BSP application set a javascript timer for 2 minutes and upon completion run a javascript to kill the backend session along with the SSO2 cookie.
check the BSP application system/session_single_frame.htm
for a javascript named "exitBSPApplication"
Hope this is helpful.
Regards
Raja

Reload previous page on back button - using cache control

Hi,
In my application I am using cache control to avoid the pages to be cached. But the requirement is changed and now the previous page can be re-loaded on hittinh browser's back button even after the 10 mins. i.e if user hits the back button with in 10 mins he should be allowed to see the pre-loaded contents on the previous page. After 10 mins the browser should display the page refresh warning.
a) Old code to preventing caching:
response.setHeader("Cache-Control","no-cache"); //HTTP 1.1
response.setHeader("Pragma","no-cache"); //HTTP 1.0
response.setDateHeader ("Expires", -1); //prevents caching at the proxy server
b) I am trying with the code ha changes as to get the previous page with in 10 minutes time:
response.setHeader("Cache-Control","no-cache, max-age=600"); //HTTP 1.1
response.setHeader("Pragma","no-cache"); //HTTP 1.0
The above code changes are not working. If uses "no-cache" with max-arg=600 it behaves like the code in section a).
If I uses response.setHeader("Cache-Control","max-age=600"); then even after 30 mins it load the previous page with preloaded contents.
Any help is appreciated.

I tried it lots of time by refreshing the browser's cache. I am using IE 6.0. I tested it through FireFox to get the header details. when I submit the request it displays the headers request
same as I set in the code. But when I hit the back button (after the max age time passed) still it gets the value from cache and no header values are displayed.

Reader X doesn't display Pdf stream if response contains header "Cache-Control: no-store, no-cache"

Hi all,
I work on a web application that, among others, generates Pdf documents. It renders them directly within the IE window by "streaming" the content of the Pdf in the response output stream. Note that we also add the header "Cache-Control", "no-store, no-cache, must-revalidate,post-check=0, pre-check=0" to the response.
Everything was fine with previous version of reader but since I installed Adobe reader X the content of the Pdf is not showing any more in my browser.
Here is what I already investigated:
- if I use another machine with an "older" Reader version, it works. If I save the displayed Pdf and try to open it on the machine where X is installed it works
- if I remove the the Cache-Control header, then it works with reader X installation
Do you have any idea what changed between version 9 and X that could lead to this issue ?
To ease diagnostic I created a sandbox environment to reproduce the problem, you can go to the following address to see what's happening (or not in case you have version X installed)
With the Cache-Control header: http://readerxissue.appspot.com
Without the Cache-Control header: http://readerxissue.appspot.com/enableCache.html
I must confess that I am a bit stuck and I wonder if some of you could help.
Thanks a lot
Regards
Vincent

Hello,
We have semiliar problems in sweden with Adobe Reader X 10.1 Swe and Internet Explorer 8.0 with streamed PDF files.
We had some issues and got them resolved by the following
Upgraded to Adobe Reader 10.1.2.45 Eng
- Print Issue:http://helpx.adobe.com/acrobat/kb/pdf-wont-print-reader-10.html
- Grey box in Internet explorer: http://helpx.adobe.com/acrobat/kb/pdf-opens-grey-screen-browser.html
- Add site as trusted: Edit-> Preferences, unbox Enable Enhanced Security + add the host/url to site that is whitelisted to send pdf files
(the Automaticly trust sites from mu Win OS security zones doesnt work for us)
The thing is we run MUI pack on our Citrix servers and want Adobe Reader in Swe but it havent been translated yet...
So we have to wait for the swedish release on Adobe Reader X 10.1.2
Thanks,
Tony Van Der Haagen
IT-Mästaren
Sweden

Controlling EJB Cache & Warning BEA-010001 in 8.1

Background: Migrated from 6.1 to 8.1. Using CMP with template.j modified (migrated).
Problem:
1. Could not use any Entities which uses Entity Cache. It throws weblogic.ejb20.cache.CacheFullException
during ejbLoad. My existing Cache parameters are (anyway, it is no different from
6.1 where itz working fine)
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
</pool>
<entity-cache>
<max-beans-in-cache>100</max-beans-in-cache>
<idle-timeout-seconds>610</idle-timeout-seconds>
<read-timeout-seconds>60</read-timeout-seconds>
<concurrency-strategy>Database</concurrency-strategy>
</entity-cache>
Is there any new configuration which needs to be set for 8.1? Redirection to
some checklist for controlling there cache parameter would be helpful?
2. While deploying my Beans it shows up Warning BEA-010001. Documentation says,
specify in weblogic-ejb-jar.xml<weblogic-ejb-jar> <disable-warning>BEA-010001
| BEA-010054</disable-warning>..</weblogic-ejb-jar>. I have thousands of beans
deployed in the server my warning message dumps my console with these messages
hiding critical error messages. Is there any 'additional parameters' to stop
this warning or route this warning to a separate log file?
TIA
JAK

Hi Jak,
max-beans-in-cache equal 100 is way too low for any real life application.
I'm not sure why it worked for you in 6.1. I remember setting it was broken
in 6.1 at some point.
Regards,
Slava Imeshev
"jak" <[email protected]> wrote in message
news:3f07e7c9$[email protected]..
>
Background: Migrated from 6.1 to 8.1. Using CMP with template.j modified(migrated).
>
Problem:
1. Could not use any Entities which uses Entity Cache. It throwsweblogic.ejb20.cache.CacheFullException
during ejbLoad. My existing Cache parameters are (anyway, it is nodifferent from
6.1 where itz working fine)
<pool>
<max-beans-in-free-pool>100</max-beans-in-free-pool>
</pool>
<entity-cache>
<max-beans-in-cache>100</max-beans-in-cache>
<idle-timeout-seconds>610</idle-timeout-seconds>
<read-timeout-seconds>60</read-timeout-seconds>
<concurrency-strategy>Database</concurrency-strategy>
</entity-cache>
Is there any new configuration which needs to be set for 8.1? Redirectionto
some checklist for controlling there cache parameter would be helpful?
2. While deploying my Beans it shows up Warning BEA-010001. Documentationsays,
specify in weblogic-ejb-jar.xml<weblogic-ejb-jar><disable-warning>BEA-010001
| BEA-010054</disable-warning>..</weblogic-ejb-jar>. I have thousands ofbeans
deployed in the server my warning message dumps my console with thesemessages
hiding critical error messages. Is there any 'additional parameters' tostop
this warning or route this warning to a separate log file?
TIA
JAK

Creating a cache control

Has anyone created a cache control for Workshop?
I'm wanting to cach the results of a complex report by using the xbean. Then if the request parameters match an already generated report, I simply send back out a pregenerated xbean.
The cache would need a time expiration and max size handling.
Thanks,
Rodger Ball
Sr. Software Architect
Business Wire.

If you have the option to use WLP, you can access the com.bea.p13n.cache APIs to write a Control that uses the portal cache functionality, which includes:
* time-to-live (LRU removal), max size configuration
* JMX based administration, including built-in admin from adminPortal and Workshop.
* cluster aware flushing.
Of course, if you can't or don't want to include portal, that won't work for you :)
Greg
Has anyone created a cache control for Workshop?
I'm wanting to cach the results of a complex report
by using the xbean. Then if the request parameters
match an already generated report, I simply send back
out a pregenerated xbean.
The cache would need a time expiration and max size
handling.
Thanks,
Rodger Ball
Sr. Software Architect
Business Wire.

Cache-Control: no-cache

Similar Messages

Maybe you are looking for