Explanation | The user entered a non-integer or non-positive integer for the priority. |
Action | Change the priority value to a positive integer. |
Explanation | The user entered a non-integer for the timeout. |
Action | Change the timeout value to a numeral integer. |
Explanation | The servlet specified was incorrectly configured. |
Action | Check that legal, non-contradictory values have been given, and that all required fields are specified. |
Explanation | A servlet was configured with trivial configuration information. This is legal, though unlikely correct, except for the simplest cases. |
Action | Verify that the servlet to be cached requires only the invocation URI to determine uniqueness. |
Explanation | A duplicate ExternalCacheGroup was entered in the configuration. |
Action | Remove the duplicate group. |
Explanation | The external cache group to which this servlet output should be forwarded was not registered in the global cache configuration. |
Action | Check the spelling of this external cache group. If correct, define this group in the global cache properties. |
Explanation | The specified error was created during the external cache adapter initialization. |
Action | Identify the cause of the error from the error-specific information that is provided in the message |
Explanation | A message was either sent or received from a cache unit that is no longer registered with this cache unit in a cache replication group. |
Action | Verify that the specified cache unit should be active; if so, restart the server. |
Explanation | When parsing the specified document, an expected XML element was not found. |
Action | Compare the XML file format to the product documentation, looking for a misconfiguration. |
Explanation | When parsing the specified configuration XML files, an expected XML element was not found. |
Action | Compare the XML file format to the product documentation, looking for a misconfiguration. |
Explanation | The specified caching properties were not specified for this application server. Caching is disabled. |
Action | Build a cache configuration XML file with the specified name. See the product documentation for instructions on how to build a cache configuration XML file. |
Explanation | Dynamic servlet caching is enabled. |
Action | None. |
Explanation | Dynamic servlet caching is disabled. |
Action | None. |
Explanation | A servlet or JSP file initialized that has a valid cache policy configured. |
Action | None. |
Explanation | General error message. |
Action | Debug the provided error. |
Explanation | Cache statistics were written to the specified file. |
Action | None. |
Explanation | This cache unit successfully joined a group of cooperating caches. |
Action | None. |
Explanation | Error loading ID Generator. |
Action | Debug the problem using the provided error message. |
Explanation | Error loading MetaData Generator. |
Action | Debug the problem using the provided error message. |
Explanation | Servlet output was marked to be replicated between caches, which requires that all request attributes are able to be serialized. |
Action | 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. |
Explanation | Unanticipated error initializing the cache. |
Action | Debug the problem using the provided error message. |
Explanation | Unanticipated error processing cache configuration. |
Action | Debug the problem using the provided error message. |
Explanation | Could not find a servlet mapping for the cache servlet or JSP file. |
Action | Correct the configuration error using the application assembly tool. |
Explanation | Duplicate exclude variables were present. |
Action | Remove the duplicate variable or incorrectly-defined exclude variables that were specified. |
Explanation | An entry was marked as externally cacheable and containes additional ID generation rules. |
Action | Remove the additional rules. |
Explanation | An error occurred while reading the cache configuration file. |
Action | Correct the error using the information that is provided in the error message. |
Explanation | An unrecognized replication policy was specified. |
Action | The valid replication policies are not-shared, shared-push, shared-pull, and shared-push-pull. |
Explanation | A cache policy specified both a component and idgenerator for the same cache ID rule. |
Action | Use either component tags or an idgenerator, but not both simultaneously. |
Explanation | A cache policy specified both a component and idgenerator for the same cache ID rule. |
Action | Use either component tags or an idgenerator, but not both simultaneously. |
Explanation | A required attribute was missing in the cache configuration. |
Action | Add the required attribute to your cache configuration file. |
Explanation | The configuration file specified multiple method or field tags for the same component. |
Action | Eliminate the duplicate method, field or both elements from the component in the configuration file. |
Explanation | The specified element must have a value of either true or false, but another value was specified. |
Action | Correct the element to have a "true" or "false" value. |
Explanation | An error occurred while trying to locate the method as specified in the cache configuration file. |
Action | Verify that the specified method in the cache configuration file exists in the object being invoked and that the method is public. |
Explanation | An error occurred while invoking the specified method to generate a cache ID. |
Action | Debug the problem using the information that is provided in the error message. |
Explanation | An error occurred while trying to locate the field as specified in the cache configuration file. |
Action | Verify that the field specified in the cache configuration file exists in the object being invoked and the field is public. |
Explanation | An error occurred while retrieving the specified field to generate a cache ID. |
Action | Debug the problem using the information that is provided in the error message. |
Explanation | An unrecognized element was encountered while parsing the cache configuration file. |
Action | Correct the document to match the cachespec.dtd file. |
Explanation | The specified component type is not valid for command caching. |
Action | Valid component types for commands are "method" and "field". |
Explanation | The cache configuration file specified a custom metadata generator for a command, but this is not supported. |
Action | See the product documentation for information on implementing the CacheableCommand.prepareMetaData method. |
Explanation | An unsupported component type was encountered while processing the specified object. |
Action | Correct the cache configuration policy to contain only valid component types for the specified object. |
Explanation | A servlet or JSP was marked Edgeable, but the cache policy contains component rules which are not valid on an IBM Edge Server. |
Action | Correct the cache policy to eliminate the rules that are not started at the IBM Edge Server, or mark the servlet or JSP file as not edgeable. |
Explanation | An unsupported component type was encountered while processing the specified servlet or JSP file. |
Action | Correct the cache configuration policy to contain only valid component types for the specified object. |
Explanation | The specified configuration file contained critical errors and cannot be utilized. |
Action | Correct the specified errors in the configuration file. |
Explanation | An XML parsing warning occurred while processing a cache configuration file. |
Action | Correct the problem that is specified in the message. |
Explanation | An XML parsing warning occurred while processing a cache configuration file. |
Action | Correct the problem that is specified in the message. |
Explanation | An error occurred while reading the cache configuration file. |
Action | Correct the problem that is specified in the message. |
Explanation | A cache configuration file was successfully processed for cache entries from the specified location. |
Action | None. |
Explanation | The dynamic cache services successfully initialized. |
Action | None. |
Explanation | The specified component type was present in the cache configuration file, but is not recognized by the cache. |
Action | Remove the unrecognized component type from the cache configuration file. |
Explanation | The specified element in the cache configuration file contained an unrecognized value. |
Action | Consult the product documentation for information on valid values for the specified element. |
Explanation | An attempt was made to use a CacheableCommand, but the servlet caching in the Web container settings is disabled. |
Action | Enable the servlet caching in the Web container settings from the administrative console. |
Explanation | The object was marked for replication between caches or saved to disk which requires the object and all referenced objects within the object to be serializable. CacheID is the ID of the cache entry that cannot be serialized. ClassName is the class name of the cached object that cannot be serialized. Type is the data type to indicate what data is being serialized. Exception is the exception received during the serialization attempt. |
Action | 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. |
Explanation | The disk offload feature is enabled for the specified cache name. The disk cache is stored in the specified directory. |
Action | None. |
Explanation | The disk offload feature is enabled for the specified cache name. The disk cache is stored in the alternate location because the specified directory cannot be created. |
Action | None. |
Explanation | The disk offload feature is disabled for the specified cache name because the disk offload location and the default alternate location cannot be created. |
Action | Make sure the disk offload location has sufficient access privileges. |
Explanation | The disk cache files were reinitialized when the server restarted due to corrupted data. This may have been caused by a Java Virtual Machine (JVM) unexpected ending or a disk exception has occurred. All old disk cache contents are lost. |
Action | None. |
Explanation | The disk cache cleanup has started to remove expired cache entries. |
Action | No user action is required. |
Explanation | The disk cache cleanup is finished. |
Action | No user action is required. |
Explanation | This shows the disk cache configuration. |
Action | No user action is required. |
Explanation | The flush to disk on stop feature is enabled for the specified cache name. |
Action | No user action is required. |
Explanation | The flush to disk on stop feature is disabled for the specified cache name. |
Action | No user action is required. |
Explanation | A cache configuration file was successfully processed for cache-instances from the specified location. |
Action | None. |
Explanation | The cached object will not be offloaded to disk because it is over the disk cache size in GB limit. |
Action | Modify the custom property "diskCacheSizeInGB" to a larger value so that it can store more caches in the disk. |
Explanation | The cached object will not be offloaded to disk because it is over the disk cache size in MB limit. |
Action | Modify the custom property "diskCacheEntrySizeInMB" to a larger value so that it can store more caches in the disk. |
Explanation | The cached object will not be offloaded to disk because it is over the disk cache size limit. |
Action | Modify the custom property "diskCacheSize" to a larger value so that it can store more caches in the disk. |
Explanation | 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. |
Action | Delete all disk cache files and then restart the server. |
Explanation | 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. |
Action | Delete all disk cache files and then restart the server. |
Explanation | The disk cache threshold limit has either been set < 0 or high threshold is lower than low threshold limit. |
Action | The disk cache threshold should be greater than 0 and high threshold limit should be greater than low threshold limit. |
Explanation | The value for custom property is not valid. Correct the value using the range-specified low and high values in the warning message. |
Action | Correct the value using the range-specified low and high values in the warning message. |
Explanation | It is required to set custom properties "diskCacheSize" or "diskCacheSizeInGB" in order to use the disk cache garbage collector feature. |
Action | Set the custom properties "diskCacheSize" or "diskCacheSizeInGB" and restart the server. |
Explanation | The disk cache files cannot shrink. |
Action | To set custom property "diskCacheSizeInGB" to a smaller value, delete all disk cache files and restart the server. |
Explanation | The disk offload feature is disabled for the specified cache name because a disk exception has occurred. |
Action | The disk cache files for this cache instance will be deleted when the server is restarted. |
Explanation | The flush to disk on stop operation has completed with the statistics. |
Action | No user action is required. |
Explanation | The named Dynamic Cache instance was successfully initialized. |
Action | None. |
Explanation | The dynamic cache instances cannot be initialized. No caches instances are avaliable. |
Action | Debug the problem using error message {0}. The application server logs contain additional information. |
Explanation | The named dynamic cache instance cannot be initialized. The named instance is not avaliable. |
Action | Debug the problem using error message {1}. The application server logs contain additional information. |
Explanation | The named dynamic cache instance cannot be initialized. Dynamic caching is disabled for the named instance. |
Action | Use the administrative console to configure a cache instance resource named {0}. |
Explanation | The named dynamic cache instance cannot be used. Dynamic caching is disabled for the named instance. |
Action | Use the administrative console to configure a cache instance resource named {0} using the correct type. |
Explanation | An exception was caught in the specified method. |
Action | None. |
Explanation | The z/OS Controller Service for the dynamic cache service has initialized successfully. |
Action | None. |
Explanation | The specified method was unable to obtain a servant proxy for DRS. |
Action | None. |
Explanation | The specified method was passed a null servant token. |
Action | None. |
Explanation | The specified method was passed a null entryKey parameter. |
Action | None. |
Explanation | The specified method cannot call the proxy because tokenBytes is null. |
Action | None. |
Explanation | The specified method cannot call the proxy because eventBytes is null. |
Action | None. |
Explanation | The specified method cannot call the proxy because entryKeyBytes is null. |
Action | None. |
Explanation | The specified method could not retrieve the cacheEntry from the push/pull table because the servant owner token is null. |
Action | None. |
Explanation | The specified method cannot call the proxy because propKeyBytes is null. |
Action | None. |
Explanation | The specified method cannot call the proxy because the DRSBootstrapMsg converted to bytes is null. |
Action | None. |
Explanation | The specified method was passed a null dbm object. |
Action | None. |
Explanation | For the specified method the returned value from proxy.handleBootstrapRequest is null. |
Action | None. |
Explanation | The specified method was passed a null propKey parameter. |
Action | None. |
Explanation | The specified method was passed a null for the value parameter. |
Action | None. |
Explanation | The specified method is unable to convert the value parameter to bytes. |
Action | None. |
Explanation | The specified method was passed a null for the DRSJvmId routing parameter. |
Action | None. |
Explanation | The specified method was passed a null for the entryKeyList. |
Action | None. |
Explanation | The specified method is unable to convert the entryKeyList parameter to a byte array. |
Action | None. |
Explanation | The specified method is unable to convert the DRSJvmID parameter to a byte array. |
Action | None. |
Explanation | The specified DynacacheDRSController DRS Instance received event REPLICATION_UP. |
Action | None. |
Explanation | The specified DynacacheDRSController DRS Instance received event REPLICATION_DOWN. |
Action | None. |
Explanation | The specified DynacacheDRSController DRS Instance received event IS_CONGESTED. |
Action | None. |
Explanation | The specified DynacacheDRSController DRS Instance received event NOT_CONGESTED. |
Action | None. |
Explanation | A required attribute was missing in the cache configuration. |
Action | Add the required attribute to your cache configuration file. |
Explanation | The low and high attribute values specified for the range are not valid. |
Action | Correct the the low and high attributes values such that the low value is less than the high value. |
Explanation | The specified element must have a value of either memory or disk, but another value was specified. |
Action | Correct the element to have the value "memory" or "disk". |
Explanation | The setting of custom property "disableDependencyId" does not match the current state of disk files. |
Action | To set custom property "disableDependencyId" to your desired settings, delete all disk cache files and restart the server. |
Explanation | The setting of custom property "disableTemplatesSupport" does not match the current state of disk files. |
Action | To set custom property "disableTemplatesSupport" to your desired settings, delete all disk cache files and restart the server. |
Explanation | Displays each cache key and its hashcode in the memory cache. |
Action | None. |
Explanation | Displays each cache key and its hashcode in the disk cache. |
Action | None. |
Explanation | Displays each cache key and its hashcode in the PushPullTable. |
Action | None. |
Explanation | Displays the total number of entries in the memory cache. |
Action | None. |
Explanation | Displays the total number of entries in the disk cache. |
Action | None. |
Explanation | Displays the total number of cache IDs in the PushPullTable. |
Action | None. |
Explanation | The cache comparsion failure might be caused by: (1) Offload to disk is enabled. When the cache instances bootstrap with one another at server startup, the disk cache entries are not replicated amongst themselves. (2) Congestion in the DRS might cause some cache updates to be dropped. (3) Some cache entries are not shareable within the replication domain. (4) The compareCaches() command will not work with the Push-Pull sharing policy. Use the compareCacheKeys command. |
Action | None. |
Explanation | The input cache instance is not valid. Configure the cache instance by using either the administrative console or the cacheinstances.properties file. |
Action | Ensure that a cache instance is configured correctly and the name of the cache instance is correct. |
Explanation | The input pattern is not a valid regular expression. |
Action | Check the java.util.regex.Pattern class. |
Explanation | Internal error: Failure to create the MessageDigest for MD5 algorithm. |
Action | Contact IBM service for debugging this problem. |
Explanation | The input node name is not valid. |
Action | Ensure that the node exists and the name is correct. |
Explanation | The input server name is not valid. |
Action | Ensure that the server exists and the name is correct. |
Explanation | Internal error: Failure to create AdminService object. |
Action | Contact IBM service for debugging this problem. |
Explanation | MBean command "CompareCaches" can only run under Deployment Manager. |
Action | Run the CompareCaches command from the Deployment Manager Dynacache MBean. |
Explanation | DynaCache MBean was not found in the node on which the server resides. |
Action | Check the query expression for the MBean. Ensure that the node and the server names provided exist. |
Explanation | Exception occurred while trying to invoke MBean command. |
Action | Find the explanation of the exception in the server SystemOut.log file. |
Explanation | The MBean command cannot be envoked because the disk offload feature is not enabled for the named cache instance. |
Action | Ensure that the disk offload feature is enabled for the named cache instance. See the Configuring dynamic cache disk offload article in the product documentation. |
Explanation | The input cache statistic name is not valid. |
Action | Ensure that the cache statistics name is valid. |
Explanation | Exception occurred while trying to invoke MBean command. |
Action | See the explanation of the exception described in the error message. |
Explanation | The Dynamic Cache (core cache) was successfully initialized. |
Action | None. |
Explanation | The Dynamic Cache (servlet cache) was successfully initialized. |
Action | None. |
Explanation | The Dynamic Cache (object cache) was successfully initialized. |
Action | None. |
Explanation | The cache instance is not added because a cache with this name already exists. |
Action | Ensure that the cache instance does not define more than once in the properties files. |
Explanation | Cache replication is disabled for cache instance because the Dynamic Cache service is running in a stand-alone server. |
Action | None. |
Explanation | The named Dynamic Servlet cache service has not be started. Servlet cache instances cannot be used. |
Action | Ensure that Dynamic servlet caching is enabled in the administrative console. |
Explanation | The named Dynamic Object cache service has not be started. Object cache instances cannot be used. |
Action | None. |
Explanation | Neither servlet cache nor object caching is enabled. |
Action | Ensure that Dynamic servlet caching is enabled in the administrative console. |
Explanation | The Dynamic Cache (core cache) failed to initialize. |
Action | Debug the problem using the provided error message. |
Explanation | This specific operation cannot be performed because cache provider does not support the alias feature. |
Action | None. |
Explanation | This specific operation cannot be performed because cache provider does not support the disk cache offload feature. |
Action | None. |
Explanation | This specific operation cannot be performed because cache provider does not support the date replication service (DRS) replication feature. |
Action | None. |
Explanation | An unanticipated error occurred while initializing the configured cache provider. The Dynamic cache will be used as cache provider to create the cache instance instead of the configured provider. |
Action | Ensure that the cache provider is provided as an Application Server runtime bundle or as a library in the Application Server lib directory. |
Explanation | The cache size in MB feature is disabled because the cached object is not implemented to be sizable. |
Action | Ensure that the cached object class implements com.ibm.websphere.cache.Sizable interface. |
Explanation | The cache size in MB feature is disabled because the configured cache provider does not support this feature. |
Action | None |
Explanation | Since memory cache size in MB or LRU trigger percent feature is enabled, the "lruToDiskTriggerTime" custom property will be changed to better value in order to get better performance. |
Action | None |
Explanation | Since the disk offload feature is disabled and cache instance is full, JVM heap space for new entries will be made available by evicting cache entries using the LRU algorithm. |
Action | Enable the disk offload feature for the cache instance to prevent the discard of cache entries from memory. |
Explanation | This shows the name of cache provider being used. |
Action | None. |
Explanation | The specified cache id will not be replicated to other servers because skipMemoryWriteToDisk is set to true. |
Action | None. |
Explanation | You must resolve the configuration error for the specified external cache group to function correctly. |
Action | None. |
Explanation | The service integration bus servers in the specified queue connection factory are no longer available. |
Action | None. |
Explanation | The external cache group is now connected to the service integration bus servers that are defined in the queue connection factory. |
Action | None. |
Explanation | The external cache group is unable to connect to the service integration bus servers that are defined in the queue connection factory. |
Action | You may need to restart the targeted service integration bus servers. |
Explanation | The name and value of a defined custom property. |
Action | None. |