com.atlassian.jira.rest.internal
Class CacheResource

java.lang.Object
  com.atlassian.jira.rest.internal.CacheResource

public class CacheResource
extends Object

Enables authorised users to manipulate and configure cache behaviour in JIRA.

Since:

v6.1

Constructor Summary

CacheResource(com.atlassian.event.api.EventPublisher eventPublisher, JiraAuthenticationContext jiraAuthenticationContext, PermissionManager permissionManager)

Method Summary

javax.ws.rs.core.Response	clearCaches() Invokes the system-wide clear cache event which should cause all caches which have subscribed to this to clear their contents completely.
javax.ws.rs.core.Response	clearClassLoaderCache() Invokes the system-wide clear cache event which should cause all caches which have subscribed to this to clear their contents completely.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

CacheResource

public CacheResource(com.atlassian.event.api.EventPublisher eventPublisher,
                     JiraAuthenticationContext jiraAuthenticationContext,
                     PermissionManager permissionManager)

Method Detail

clearCaches

public javax.ws.rs.core.Response clearCaches()

Invokes the system-wide clear cache event which should cause all caches which have subscribed to this to clear their contents completely. Typical configuration ensures that it will happen asynchronously although that is not guaranteed. Note that requests to the application after calling this may take an initial performance hit until the relevant caches are warmed up again.

The intended purpose of this is to shrink the memory usage of a JIRA instance which is not being actively used.

clearClassLoaderCache

public javax.ws.rs.core.Response clearClassLoaderCache()

Invokes the system-wide clear cache event which should cause all caches which have subscribed to this to clear their contents completely. Typical configuration ensures that it will happen asynchronously although that is not guaranteed. Note that requests to the application after calling this may take an initial performance hit until the relevant caches are warmed up again.

The intended purpose of this is to shrink the memory usage of a JIRA instance which is not being actively used.