Problem | The user entered a non-integer or non-positive integer for the priority. |
User response | Change the priority value to a positive integer. |
Problem | The user entered a non-integer for the timeout. |
User response | Change the timeout value to a numeral integer. |
Problem | The servlet specified was incorrectly configured for an unknown reason. |
User response | Check that legal, non-contradictory values have been given, and that all required fields are specified. |
Problem | A servlet was configured with trivial configuration information. This is legal, though unlikely correct, except for the simplest cases. |
User response | Verify that the servlet to be cached requires only the invocation URI to determine uniqueness. |
Problem | A duplicate ExternalCacheGroup was entered in the configuration. |
User response | Remove the duplicate group. |
Problem | The external cache group to which this servlet output should be forwarded, was not registered in the global cache configuration. |
User response | Check the spelling of this external cache group. If correct, define this group in the global cache properties. |
Problem | The specified error was thrown during external cache adapter initialization. |
User response | Identify the cause of the error from the error specific information provided in the message |
Problem | A message was either sent or received from a cache unit that is no longer registered with this cache unit with a cache replication group. |
User response | Verify that the specified cache unit should be active; if so, restart the server. |
Problem | When parsing the document specified, an expected XML element was not found. |
User response | Check the XML file format against the documentation, looking for a misconfiguration. |
Problem | When parsing the configuration XML files, an expected XML element was not found. |
User response | Check the XML file format against the documentation, looking for a misconfiguration. |
Problem | The specified caching properties were not specified for this application server. Caching is disabled. |
User response | Build a cache configuration XML file with the specified name. See documentation for instructions on building this file. |
Problem | Dynamic servlet caching is enabled. |
User response | None. |
Problem | Dynamic servlet caching is disabled. |
User response | None. |
Problem | A servlet or JSP was initialized that has a valid cache policy configured. |
User response | None. |
Problem | General error message. |
User response | Debug the provided error. |
Problem | Cache statistics were written to the specified file. |
User response | None. |
Problem | This cache unit successfully joined a group of cooperating caches. |
User response | None. |
Problem | Error loading ID Generator. |
User response | Debug the problem using the provided error message. |
Problem | Error loading MetaData Generator. |
User response | Debug the problem using the provided error message. |
Problem | Servlet output was marked to be replicated between caches, which requires that all request attributes are able to be serialized. |
User response | Modify the cache policy for this servlet so that its output is not replicated, or modify the application so that all request attributes can be serialized. |
Problem | Unanticipated error initializing the cache. |
User response | Debug the problem using the provided error message. |
Problem | Unanticipated error processing cache configuration. |
User response | Debug the problem using the provided error message. |
Problem | Could not find a servlet mapping for the cache servlet or JSP. |
User response | Correct the configuration error using the application assembly tool. |
Problem | Duplicate exclude variables were present. |
User response | Remove the duplicate or incorrectly defined excludes variables that were specified. |
Problem | An entry was marked as externally cacheable, but also contained additional id generation rules. |
User response | Remove the additional rules. |
Problem | An error occurred while reading the cache configuration file. |
User response | Correct the error using the provided information. |
Problem | An unrecognized replication policy was specified. |
User response | The valid replication policies are not-shared, shared-push, shared-pull, and shared-push-pull. |
Problem | A cache policy specified both a component and idgenerator for the same cache id rule. |
User response | You must either use either component tags or an idgenerator but not both simultaneously. |
Problem | A cache policy specified both a component and idgenerator for the same cache id rule. |
User response | You must either use either component tags or an idgenerator but not both simultaneously. |
Problem | A required attribute was missing in the cache configuration. |
User response | Add the required attribute to your cache configuration file. |
Problem | The configuration file specified multiple method or field tags for the same component. |
User response | Eliminate the duplicate method and/or field elements from the component in the configuration file. |
Problem | The specified element must have a value of either true or false, but another value was specified. |
User response | Correct the element to have the value "true" or "false". |
Problem | An error occurred while trying to locate the specified method as specified in the cache configuration file. |
User response | Verify that the method specified in the cache configuration file exists in the object being invoked and the method is public. |
Problem | An error occurred while invoking the specified method to generate a cache id. |
User response | Debug the problem using the provided error message. |
Problem | An error occurred while trying to locate the specified field as specified in the cache configuration file. |
User response | Verify that the field specified in the cache configuration file exists in the object being invoked and the field is public. |
Problem | An error occurred while retrieving the specified field to generate a cache id. |
User response | Debug the problem using the provided error message. |
Problem | An unrecognized element was encountered while parsing the cache configuration file. |
User response | Correct the document to match the cachespec.dtd. |
Problem | The specified component type is not valid for command caching. |
User response | Valid component types for commands are "method" and "field". |
Problem | The cache configuration file specified a custom metadata generator for a command, but this is not supported. |
User response | Read the product documentation on implementing the CacheableCommand.prepareMetaData method. |
Problem | An unsupported component type was encountered while processing the specified object. |
User response | Correct the cache configuration policy to contain only valid component types for the specified object. |
Problem | A servlet or JSP was marked Edgeable, but the cache policy contains component rules which are not valid on an edge server. |
User response | Correct the cache policy to eliminate the rules that are not executable at the Edge Server, or mark the servlet/JSP as not edgeable. |
Problem | An unsupported component type was encounted while processing the specified servlet or JSP. |
User response | Correct the cache configuration policy to contain only valid component types for the specified object. |
Problem | The specified configuration file contained critical errors and cannot be utilized. |
User response | Correct the specified errors in the configuration file. |
Problem | An XML parsing warning occurred while processing a cache configuration file. |
User response | Correct the problem specified in the message. |
Problem | An XML parsing warning occurred while processing a cache configuration file. |
User response | Correct the problem specified in the message. |
Problem | An error occurred while reading the cache configuration file. |
User response | Correct the problem specified in the message. |
Problem | This message indicates that a cache configuration file was successfully processed for cache-entries from the specified location. |
User response | None. |
Problem | This message indicates that the WebSphere Dynamic Cache was successfully initialized. |
User response | None. |
Problem | The specified component type was present in the cache configuration file, but is not recognized by the cache. |
User response | Remove the unrecognized component type from the cache configuration file. |
Problem | The specified element in the cache configuration file contained an unrecognized value. |
User response | Consult the WebSphere documentation for valid values for the specified element. Correct the problem. |
Problem | An attempt was made to use a CacheableCommand, but WebSphere Dynamic Caching is disabled. |
User response | Enable the WebSphere Dynamic Cache so that the command can be cached. |
Problem | The object was marked to be replicated between caches or saved to disk which requires the object and all referenced objects within the object be serializable. CacheID is the id of the cache entry that can not be serialized. ClassName is the class name of the cached object that can not be serialized. Exception is the exception received during the serialization attempt. |
User response | Modify the cache policy for this object so that it is not replicated or saved to disk or modify the application so the object and all referenced objects are serializable. |
Problem | This message indicates that offload to disk is enabled for the specified cache name. The disk cache is stored in the specified directory. |
User response | None. |
Problem | This message indicates that offload to disk is enabled for the specified cache name. The disk cache is stored in the alternate location because specified directory cannot be created. |
User response | None. |
Problem | This message indicates that offload to disk is disabled for the specified cache name because disk offload location and default alternate location cannot be created. |
User response | Make sure the disk offload location has sufficient access privileges. |
Problem | This message indicates that the disk cache files have been reinitialized because of corrupted data. This may have been caused by an unexpected JVM termination or a disk exception occurred before the server was restarted. All old disk cache contents are lost. |
User response | None. |
Problem | This message indicates that the disk cache cleanup has started to remove expired cache entries. |
User response | No user action is required. |
Problem | This message indicates that the disk cache cleanup is finished. |
User response | No user action is required. |
Problem | This message shows the disk cache configuration. |
User response | No user action is required. |
Problem | This message indicates that flush to disk on stop is enabled for the specified cache name |
User response | No user action is required. |
Problem | This message indicates that flush to disk on stop is disabled for the specified cache name |
User response | No user action is required. |
Problem | This message indicates that a cache configuration file was successfully processed for cache-instances from the specified location. |
User response | None. |
Problem | The cached object will not be offloaded to disk because it is over the disk cache size in GB limit. |
User response | Modify the custom property "diskCacheSizeInGB" to a larger value so that it can store more caches in the disk. |
Problem | The cached object will not be offloaded to disk because it is over the disk cache size in MB limit. |
User response | Modify the custom property "diskCacheEntrySizeInMB" to a larger value so that it can store more caches in the disk. |
Problem | The cached object will not be offloaded to disk because it is over the disk cache size limit. |
User response | Modify the custom property "diskCacheSize" to a larger value so that it can store more caches in the disk. |
Problem | The disk files on the system are in an old format and the limiting disk cache size in GB feature uses a new disk format. Before enabling this feature delete all disk cache files on the system. |
User response | Delete all disk cache files and then restart the server. |
Problem | The disk files on the system are in an old format and the disk cache garbage collection feature uses a new disk format. Before enabling this feature delete all disk cache files on the system. |
User response | Delete all disk cache files and then restart the server. |
Problem | The disk cache threshold limit has either been set < 0 or high threshold is lower than low threshold limit. |
User response | The disk cache threshold should be greater than 0 and high threshold limit should be greater than low threshold limit. |
Problem | An invalid value for custom property is found. Correct the value using the range-specified low and high values in the warning message. |
User response | Correct the value using the range-specified low and high values in the warning message. |
Problem | It is required to set custom properties "diskCacheSize" or "diskCacheSizeInGB" in order to use the disk cache garbage collector feature. |
User response | Set the custom properties "diskCacheSize" or "diskCacheSizeInGB" and restart the server. |
Problem | The disk cache files cannot shrink. |
User response | To set custom property "diskCacheSizeInGB" to a smaller value, delete all disk cache files and restart the server. |
Problem | This message indicates that offload to disk is disabled for the specified cache name because a disk exception has occurred. |
User response | The disk cache files for this cache instance will be deleted when the server is restarted. |
Problem | This message indicates that flush to disk on stop operation has completed with the statistics. |
User response | No user action is required. |
Problem | This message indicates the named WebSphere Dynamic Cache instance was successfully initialized. |
User response | None. |
Problem | This message indicates the WebSphere Dynamic Cache instances can not be initialized. No caches instances are avaliable. |
User response | Debug the problem using error message {0}. The WebSphere logs will contain additional information. |
Problem | This message indicates the named WebSphere Dynamic Cache instance can not be initialized. The named instance is not avaliable. |
User response | Debug the problem using error message {1}. The WebSphere logs will contain additional information. |
Problem | This message indicates the named WebSphere Dynamic Cache instance can not be initialized. Dynamic caching is disabled for the named instance. |
User response | Use the WebSphere Administrative Console to configure a cache instance resource named {0}. |
Problem | This message indicates the named WebSphere Dynamic Cache instance can not be used. Dynamic caching is disabled for the named instance. |
User response | Use the WebSphere Administrative Console to configure a cache instance resource named {0} using the correct type. |
Problem | An exception was caught in the specified method. |
User response | None. |
Problem | The z/OS Controller Service for Dynacache has initialized successfully. |
User response | None. |
Problem | The specified method was unable to obtain a servant proxy for DRS. |
User response | None. |
Problem | The specified method was passed a null servant token. |
User response | None. |
Problem | The specified method was passed a null entryKey parameter. |
User response | None. |
Problem | The specified method cannot call the proxy because tokenBytes is null. |
User response | None. |
Problem | The specified method cannot call the proxy because eventBytes is null. |
User response | None. |
Problem | The specified method cannot call the proxy because entryKeyBytes is null. |
User response | None. |
Problem | The specified method could not retrieve the cacheEntry from the push/pull table because the servant owner token is null. |
User response | None. |
Problem | The specified method cannot call the proxy because propKeyBytes is null. |
User response | None. |
Problem | The specified method cannot call the proxy because the DRSBootstrapMsg converted to bytes is null. |
User response | None. |
Problem | The specified method was passed a null dbm object. |
User response | None. |
Problem | For the specified method the returned value from proxy.handleBootstrapRequest is null. |
User response | None. |
Problem | The specified method was passed a null propKey parameter. |
User response | None. |
Problem | The specified method was passed a null for the value parameter. |
User response | None. |
Problem | The specified method is unable to convert the value parameter to bytes. |
User response | None. |
Problem | The specified method was passed a null for the DRSJvmId routing parameter. |
User response | None. |
Problem | The specified method was passed a null for the entryKeyList. |
User response | None. |
Problem | The specified method is unable to convert the entryKeyList parameter to a byte array. |
User response | None. |
Problem | The specified method is unable to convert the DRSJvmID parameter to a byte array. |
User response | None. |
Problem | The specified DynacacheDRSController DRS Instance received event REPLICATION_UP. |
User response | None. |
Problem | The specified DynacacheDRSController DRS Instance received event REPLICATION_DOWN. |
User response | None. |
Problem | The specified DynacacheDRSController DRS Instance received event IS_CONGESTED. |
User response | None. |
Problem | The specified DynacacheDRSController DRS Instance received event NOT_CONGESTED. |
User response | None. |
Problem | A required attribute was missing in the cache configuration. |
User response | Add the required attribute to your cache configuration file. |
Problem | The low and high attribute values specified for the range are not valid. |
User response | Correct the the low and high attributes values such that the low value is less than the high value. |
Problem | The specified element must have a value of either memory or disk, but another value was specified. |
User response | Correct the element to have the value "memory" or "disk". |
Problem | The setting of custom property "disableDependencyId" does not match the current state of disk files. |
User response | To set custom property "disableDependencyId" to your desired settings, delete all disk cache files and restart the server. |
Problem | The setting of custom property "disableTemplatesSupport" does not match the current state of disk files. |
User response | To set custom property "disableTemplatesSupport" to your desired settings, delete all disk cache files and restart the server. |