External cache invalidation
The responsibility for synchronizing the dynamic cache of external caches and the WAS is shared by both systems. For example, a public Web page dynamically created and cached at the appserver using Servlet/JSP result caching can be exported by the application server and cached by the external cache server, which can serve the application's execution results repeatedly to many different users until notified that the page is invalid.
The content in the external cache is valid until:
The proxy server removes an entry because the cache is congested. Or the default timeout set by the Caching Proxy's configuration file expires. Or the Caching Proxy receives an Invalidate message directing it to purge the content from its cache. Invalidate messages originate at the WAS that owns the content and are propagated to each configured Caching Proxy.
Prev | Home | Next WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.