Express (Distributed operating systems), v8.0 > Reference > Messages
DYNA
DYNA0001E: The priority value was not a valid number for entry {0}. Use an integer instead of {1}.
Explanation The user entered a non-integer or non-positive integer for the priority. Action Change the priority value to a positive integer.
DYNA0002E: The timeout value was not a valid number for entry {0}. Use an integer instead of {1}.
Explanation The user entered a non-integer for the timeout. Action Change the timeout value to a numeral integer.
DYNA0003E: Not caching {0} due to misconfiguration.
Explanation The servlet specified was incorrectly configured. Action Check that legal, non-contradictory values have been given, and that all required fields are specified.
DYNA0004E: A default cache entry generator was created, but given no configuration information. This generator will use the URI with no parameters to generate cache IDs. This information should be set in the servletcache.xml file.
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.
DYNA0005E: Duplicate ExternalCacheGroup entry for address {0}.
Explanation A duplicate ExternalCacheGroup was entered in the configuration. Action Remove the duplicate group.
DYNA0006E: ExternalCacheGroup {0} was not found.
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.
DYNA0007E: Error initializing external cache adapter: {0}
Explanation The specified error was created during the external cache adapter initialization. Action Identify the cause of the error from the error-specific information provided in the message
DYNA0008E: CacheUnit no longer exists.
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.
DYNA0009E: No element named {0} in document {1}.
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.
DYNA0010E: No element named {0} in {1}.
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.
DYNA0011E: Servlet cache file {0} not found; caching is disabled
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.
DYNA0012I: Dynamic servlet caching is enabled
Explanation Dynamic servlet caching is enabled. Action None.
DYNA0013I: Dynamic servlet caching is disabled
Explanation Dynamic servlet caching is disabled. Action None.
DYNA0014I: {0} is a cacheable URI
Explanation A servlet or JSP file initialized that has a valid cache policy configured. Action None.
DYNA0015I: Dynamic Servlet Caching encountered an error: {0}
Explanation General error message. Action Debug the provided error.
DYNA0016I: Dumped dynamic servlet caching statistics to: {0}
Explanation Cache statistics were written to the specified file. Action None.
DYNA0017I: Joined group {0}
Explanation This cache unit successfully joined a group of cooperating caches. Action None.
DYNA0018E: Error loading ID Generator {0}
Explanation Error loading ID Generator. Action Debug the problem using the provided error message.
DYNA0019E: Error loading MetaData Generator {0}
Explanation Error loading MetaData Generator. Action Debug the problem using the provided error message.
DYNA0020E: Unable to cache {0}, request attributes can not be serialized.
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.
DYNA0021E: Unable to initialize cache unit {0}: {1}
Explanation Unanticipated error initializing the cache. Action Debug the problem using the provided error message.
DYNA0022E: Error processing dynamic cache configuration: {0}
Explanation Unanticipated error processing cache configuration. Action Debug the problem using the provided error message.
DYNA0023E: Error building cache policy {0}. There are no servlet mappings defined for servlet {1}
Explanation Could not find a servlet mapping for the cache servlet or JSP file. Action Correct the configuration error using the application assembly tool.
DYNA0024E: Error building cache policy {0}. "Exclude" variables were duplicates or incorrectly defined for cache variable {1}.
Explanation Duplicate exclude variables were present. Action Remove the duplicate variable or incorrectly-defined exclude variables that were specified.
DYNA0025E: Externally caching a servlet automatically uses all request parameters and nothing more in building cache ids. Request parameters may be defined for externally cacheable ONLY for use with the exclude, invalidate, and dataid functions.
Explanation An entry was marked as externally cacheable and containes additional ID generation rules. Action Remove the additional rules.
DYNA0026E: Error reading element {0}. While processing value {1}, received exception: {2}.
Explanation An error occurred while reading the cache configuration file. Action Correct the error using the information provided in the error message.
DYNA0027E: Unrecognized replication policy: {0}.
Explanation An unrecognized replication policy was specified. Action The valid replication policies are not-shared, shared-push, shared-pull, and shared-push-pull.
DYNA0028E: Illegal use of component {0} when idgenerator {1} is already defined.
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.
DYNA0029E: Illegal use of idgenerator {0} when component {1} is already defined.
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.
DYNA0030E: {0} element is missing required attribute "{1}".
Explanation A required attribute was missing in the cache configuration. Action Add the required attribute to your cache configuration file.
DYNA0031E: Illegal use of element {0} with id {1}. Field or method element is already present.
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.
DYNA0032E: Element or attribute "{0}" must be set to either the value "true" or "false". Value present: {0}.
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.
DYNA0033E: Unable to introspect method {0} from class {1}. Exception: {2}
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.
DYNA0034E: Exception invoking method {0} on class {1}. Exception: {2}
Explanation An error occurred while invoking the specified method to generate a cache ID. Action Debug the problem using the information provided in the error message.
DYNA0035E: Unable to introspect field {0} from class {1}. Exception: {2}
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.
DYNA0036E: Exception retrieving field {0} from class {1}. Exception: {2}
Explanation An error occurred while retrieving the specified field to generate a cache ID. Action Debug the problem using the information provided in the error message.
DYNA0037E: Unrecognized element {0} while processing element {1}.
Explanation An unrecognized element was encountered while parsing the cache configuration file. Action Correct the document to match the cachespec.dtd file.
DYNA0038E: Unrecognized component type {0} for command {1}.
Explanation The specified component type is not valid for command caching. Action Valid component types for commands are "method" and "field".
DYNA0039E: Commands do not support custom metadata generating classes. We must override the prepareMetaData() method.
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.
DYNA0040E: Illegal component type {0} servicing {1}.
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.
DYNA0041E: Invalid component type {0} for edgeable fragment {1}.
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.
DYNA0042E: Invalid component type {0} for servlet/jsp fragment {1}.
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.
DYNA0043E: Configuration file {0} contained errors and will not be used.
Explanation The specified configuration file contained critical errors and cannot be utilized. Action Correct the specified errors in the configuration file.
DYNA0044E: XML parsing warning: {0}, while parsing file {1} at line {2}, column {3}.
Explanation An XML parsing warning occurred while processing a cache configuration file. Action Correct the problem specified in the message.
DYNA0045E: XML parsing error: {0}, while parsing file {1} at line {2}, column {3}.
Explanation An XML parsing warning occurred while processing a cache configuration file. Action Correct the problem specified in the message.
DYNA0046E: I/O exception {0} occurred while processing configuration file {1}.
Explanation An error occurred while reading the cache configuration file. Action Correct the problem specified in the message.
DYNA0047I: Successfully loaded cache-entries from cache configuration file {0}.
Explanation A cache configuration file was successfully processed for cache entries from the specified location. Action None.
DYNA0048I: WebSphere Dynamic Cache initialized successfully.
Explanation The dynamic cache services successfully initialized. Action None.
DYNA0049E: Unrecognized component type {0}.
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.
DYNA0050E: Unrecognized value {0} for element {1}.
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.
DYNA0051E: Could not cache a CacheableCommand because WebSphere Dynamic Caching is disabled.
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.
DYNA0052E: The cached object can not be replicated or saved to disk. CacheID={0} ClassName={1} Type={2} Exception={3}
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.
DYNA0053I: Offload to disk is enabled for cache named "{0}" in directory "{1}".
Explanation The disk offload feature is enabled for the specified cache name. The disk cache is stored in the specified directory. Action None.
DYNA0054W: Offload to disk is enabled for cache name "{0}". The location "{1}" cannot be created. The default alternate location "{2}" is used instead.
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.
DYNA0055E: Offload to disk is disabled for cache name "{0}" because the location "{1}" or "{2}" cannot be created.
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.
DYNA0056W: Disk cache files have been reinitialized because of corrupted data.
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.
DYNA0057I: The disk cache cleanup started for the cache name "{0}". The statistics are: {1}
Explanation The disk cache cleanup has started to remove expired cache entries. Action No user action is required.
DYNA0058I: The disk cache cleanup finished for cache name "{0}". The statistics are: {1}
Explanation The disk cache cleanup is finished. Action No user action is required.
DYNA0059I: The disk cache configuration for cache name "{0}". The configuration is: {1}
Explanation This shows the disk cache configuration. Action No user action is required.
DYNA0060I: Flush to disk on stop is enabled for cache name "{0}".
Explanation The flush to disk on stop feature is enabled for the specified cache name. Action No user action is required.
DYNA0061I: Flush to disk on stop is disabled for cache name "{0}".
Explanation The flush to disk on stop feature is disabled for the specified cache name. Action No user action is required.
DYNA0062I: Successfully loaded cache-instances from configuration file {0}.
Explanation A cache configuration file was successfully processed for cache-instances from the specified location. Action None.
DYNA0063W: The disk cache size has reached the limit {0} GB for cache name "{1}". {2} cache entries were evicted from memory but not offloaded to disk.
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.
DYNA0064W: The size of cache entry is over limit {0} MB for cache name "{1}". {2} cache entries were evicted from memory but not offloaded to 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.
DYNA0065W: The disk cache size is over limit {0} for cache name "{1}". {2} cache entries were evicted from memory but not offloaded to 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.
DYNA0066W: The feature of limiting disk cache size in GB is disabled for the cache name "{0}". The custom property "diskCacheSizeInGB" is set to 0. Delete all disk cache files under the directory "{1}" before this feature is enabled.
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.
DYNA0067W: The disk cache garbage collector is disabled and Eviction Policy is set to "NONE" for the cache name "{0}". Delete all disk cache files under the directory "{1}" before this feature is enabled.
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.
DYNA0068W: Invalid disk threshold set for cache name "{0}". Using default values of 80% and 70% for high and low threshold limits respectively.
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.
DYNA0069W: An invalid value "{0}" for custom property "{1}" in cache name "{2}". The valid range is low: "{3}" and high: "{4}". This custom property is set to "{5}".
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.
DYNA0070W: The disk cache garbage collector is disabled and Eviction Policy is set to "NONE" for the cache name "{0}". This is because disk cache size or disk cache in GB limit are not set.
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.
DYNA0071W: The custom property "diskCacheSizeInGB" for cache name "{0}" is set to a larger value "{1}" because total disk cache files size has a larger value. To set "diskCacheSizeInGB" to a smaller value, delete all disk cache files under the directory "{2}".
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.
DYNA0072E: Offload to disk is disabled for cache name "{0}" because a disk exception has occurred. The disk offload location is in "{1}". Exception: "{2}".
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.
DYNA0073I: Flush to disk on stop for cache name "{0}" has completed. The statistics are: {1}
Explanation The flush to disk on stop operation has completed with the statistics. Action No user action is required.
DYNA1001I: WebSphere Dynamic Cache instance named {0} initialized successfully.
Explanation The named Dynamic Cache instance was successfully initialized. Action None.
DYNA1002E: WebSphere Dynamic Cache instances can not be initialized because of error {0}.
Explanation The dynamic cache instances cannot be initialized. No caches instances are avaliable. Action Debug the problem using the error message. The application server logs contain additional information.
DYNA1003E: WebSphere Dynamic Cache instance named {0} can not be initialized because of error {1}.
Explanation The named dynamic cache instance cannot be initialized. The named instance is not avaliable. Action Debug the problem using the error message. The application server logs contain additional information.
DYNA1004E: WebSphere Dynamic Cache instance named {0} can not be initialized because it is not configured.
Explanation The named dynamic cache instance cannot be initialized. Dynamic caching is disabled for the named instance. Action Use the administrative console to configure the cache instance resource.
DYNA1005E: WebSphere Dynamic Cache instance named {0} can not be accessed because it is the wrong type.
Explanation The named dynamic cache instance cannot be used. Dynamic caching is disabled for the named instance. Action Use the administrative console to configure the cache instance resource using the correct type.
DYNA1006E: Method {0} caught exception: {1}
Explanation An exception was caught in the specified method. Action None.
DYNA1007I: {0} service has initialized successfully.
Explanation The z/OS Controller Service for the dynamic cache service has initialized successfully. Action None.
DYNA1008E: Method {0}: proxy is null.
Explanation The specified method was unable to obtain a servant proxy for DRS. Action None.
DYNA1009E: Method {0}: token is null.
Explanation The specified method was passed a null servant token. Action None.
DYNA1010E: Method {0}: Parameter error: entryKey is null.
Explanation The specified method was passed a null entryKey parameter. Action None.
DYNA1011E: Method {0}: tokenBytes is null: token = {1} tokenBytes = {2}
Explanation The specified method cannot call the proxy because tokenBytes is null. Action None.
DYNA1012E: Method {0}: eventBytes is null: event = {1} eventBytes = {2}
Explanation The specified method cannot call the proxy because eventBytes is null. Action None.
DYNA1013E: Method {0}: entryKeyBytes is null: entryKey = {1} entryKeyBytes = {2}
Explanation The specified method cannot call the proxy because entryKeyBytes is null. Action None.
DYNA1014E: Method {0}: Entry should have been in our push/pull table, but servant token is null. entryKey = {1}
Explanation The specified method could not retrieve the cacheEntry from the push/pull table because the servant owner token is null. Action None.
DYNA1015E: Method {0}: propKeyBytes is null: propKey = {1} propKeyBytes = {2}
Explanation The specified method cannot call the proxy because propKeyBytes is null. Action None.
DYNA1016E: Method {0}: dbmBytes is null: dbm = {1} dbmBytes = {2}
Explanation The specified method cannot call the proxy because the DRSBootstrapMsg converted to bytes is null. Action None.
DYNA1017E: Method {0}: Parameter error: dbm is null.
Explanation The specified method was passed a null dbm object. Action None.
DYNA1018E: Method {0}: Value tmp returned by proxy.handleBootstrapRequest is null: tmp = {1}, token = {2}
Explanation For the specified method the returned value from proxy.handleBootstrapRequest is null. Action None.
DYNA1019E: Method {0}: Parameter error: propKey is null.
Explanation The specified method was passed a null propKey parameter. Action None.
DYNA1020E: Method {0}: Parameter error: value is null.
Explanation The specified method was passed a null for the value parameter. Action None.
DYNA1021E: Method {0}: Cannot convert the value parameter to bytes.
Explanation The specified method is unable to convert the value parameter to bytes. Action None.
DYNA1022E: Method {0}: Parameter error: DRSJvmId routing information is null.
Explanation The specified method was passed a null for the DRSJvmId routing parameter. Action None.
DYNA1023E: Method {0}: Parameter error: entryKeyList is null.
Explanation The specified method was passed a null for the entryKeyList. Action None.
DYNA1024E: Method {0}: Cannot convert the entryKeyList to bytes - entryKeyList = {1} entryKeyListBytes = {2}
Explanation The specified method is unable to convert the entryKeyList parameter to a byte array. Action None.
DYNA1025E: Method {0}: Cannot convert the DRSJvmId to bytes - jvmId = {1} jvmIdBytes = {2}
Explanation The specified method is unable to convert the DRSJvmID parameter to a byte array. Action None.
DYNA1026I: DynacacheDRSController DRS Instance {0} received event REPLICATION_UP.
Explanation The specified DynacacheDRSController DRS Instance received event REPLICATION_UP. Action None.
DYNA1027I: DynacacheDRSController DRS Instance {0} received event REPLICATION_DOWN.
Explanation The specified DynacacheDRSController DRS Instance received event REPLICATION_DOWN. Action None.
DYNA1028I: DynacacheDRSController DRS Instance {0} received event IS_CONGESTED.
Explanation The specified DynacacheDRSController DRS Instance received event IS_CONGESTED. Action None.
DYNA1029I: DynacacheDRSController DRS Instance {0} received event NOT_CONGESTED.
Explanation The specified DynacacheDRSController DRS Instance received event NOT_CONGESTED. Action None.
DYNA1030E: Invalid range values, low: {0} and high: {1} attributes must be integers
Explanation A required attribute was missing in the cache configuration. Action Add the required attribute to your cache configuration file.
DYNA1031E: Invalid range, low atribute: {0} is greater than high attribute: {1}.
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.
DYNA1032E: Property with name "primary-storage" must be set to either the value "memory" or "disk". Value present: {0}.
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".
DYNA1033W: Custom property "disableDependencyId" is set to {0} which does not match with the current state of disk files for cache name "{1}". The custom property "disableDependencyId" is set to {2}.
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.
DYNA1034W: Custom property "disableTemplatesSupport" is set to {0} which does not match with the current state of disk files for cache name "{1}". The custom property "disableTemplatesSupport" is set to {2}.
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.
DYNA1035I: List of {0} cache keys and their hashcodes in the memory cache for cache name "{1}": {2}
Explanation Displays each cache key and its hashcode in the memory cache. Action None.
DYNA1036I: List of {0} cache keys and their hashcodes in the disk cache for cache name "{1}": {2}
Explanation Displays each cache key and its hashcode in the disk cache. Action None.
DYNA1037I: List of {0} cache keys and their hashcodes in the PushPullTable for cache name "{1}": {2}
Explanation Displays each cache key and its hashcode in the PushPullTable. Action None.
DYNA1038I: Total number of cache entries in the memory cache is {0} for cache name "{1}".
Explanation Displays the total number of entries in the memory cache. Action None.
DYNA1039I: Total number of cache entries in the disk cache is {0} for cache name "{1}".
Explanation Displays the total number of entries in the disk cache. Action None.
DYNA1040I: Total number of cache IDs in the PushPullTable is {0} for cache name "{1}".
Explanation Displays the total number of cache IDs in the PushPullTable. Action None.
DYNA1041W: Cache comparsion between server1 "{0}" and server2 "{1}" for cache name "{2}" failed.
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.
DYNA1042E: The input cache instance "{0}" is not valid or is not configured.
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.
DYNA1043E: The input pattern "{0}" is not a valid regular expression. Exception: {1}
Explanation The input pattern is not a valid regular expression. Action Check the java.util.regex.Pattern class.
DYNA1044E: Internal error: Failure to create the MessageDigest for MD5 algorithm. Exception: {0}
Explanation Internal error: Failure to create the MessageDigest for MD5 algorithm. Action Contact IBM service for debugging this problem.
DYNA1045E: The input node "{0}" is not a valid node name.
Explanation The input node name is not valid. Action Ensure that the node exists and the name is correct.
DYNA1046E: The input server "{0}" is not a valid server name.
Explanation The input server name is not valid. Action Ensure that the server exists and the name is correct.
DYNA1047E: Internal error: Failure to create AdminService object. Exception: {0}
Explanation Internal error: Failure to create AdminService object. Action Contact IBM service for debugging this problem.
DYNA1048E: MBean command "{0}" can only run under Deployment Manager.
Explanation MBean command "CompareCaches" can only run under Deployment Manager. Action Run the CompareCaches command from the Deployment Manager Dynacache MBean.
DYNA1049E: DynaCache MBean was not found in the node "{0}" on which the server "{1}" resides.
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.
DYNA1050E: Exception occurred while trying to invoke MBean command "{0}" in the server "{1}". Exception: {2}
Explanation Exception occurred while trying to invoke MBean command. Action Find the explanation of the exception in the server SystemOut.log file.
DYNA1051E: The MBean command "{0}" cannot be performed because the disk offload feature is not enabled for named cache instance "{1}".
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.
DYNA1052E: The input name "{0}" is not a valid cache statistic name.
Explanation The input cache statistic name is not valid. Action Ensure that the cache statistics name is valid.
DYNA1053E: Exception occurred while trying to invoke MBean command "{0}". Exception: {1}
Explanation Exception occurred while trying to invoke MBean command. Action See the explanation of the exception described in the error message.
DYNA1054I: Dynamic Cache (core cache) initialized successfully.
Explanation The Dynamic Cache (core cache) was successfully initialized. Action None.
DYNA1055I: Dynamic Cache (servlet cache) initialized successfully.
Explanation The Dynamic Cache (servlet cache) was successfully initialized. Action None.
DYNA1056I: Dynamic Cache (object cache) initialized successfully.
Explanation The Dynamic Cache (object cache) was successfully initialized. Action None.
DYNA1057W: Cache instance "{0}" defined in the "{1}" is not added because a cache with this name already exists.
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.
DYNA1058W: Cache replication is disabled for cache instance "{0}" because the Dynamic Cache service is running in a stand-alone server.
Explanation Cache replication is disabled for cache instance because the Dynamic Cache service is running in a stand-alone server. Action None.
DYNA1059W: Dynamic Cache instance named {0} cannot be used because the Dynamic Servlet cache service has not been started.
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.
DYNA1060W: Dynamic Cache instance named {0} cannot be used because the Dynamic Object cache service has not been started.
Explanation The named Dynamic Object cache service has not be started. Object cache instances cannot be used. Action None.
DYNA1061E: Neither servlet cache nor object caching is enabled.
Explanation Neither servlet cache nor object caching is enabled. Action Ensure that Dynamic servlet caching is enabled in the administrative console.
DYNA1062E: Dynamic Cache (core cache) failed to initialize. Exception: {0}
Explanation The Dynamic Cache (core cache) failed to initialize. Action Debug the problem using the provided error message.
DYNA1063E: The operation "{0}" for cacheName "{1}" cannot be performed because cache provider "{2}" does not support the alias feature.
Explanation This specific operation cannot be performed because cache provider does not support the alias feature. Action None.
DYNA1064E: The operation "{0}" for cacheName "{1}" cannot be performed because cache provider "{2}" does not support the disk cache offload feature.
Explanation This specific operation cannot be performed because cache provider does not support the disk cache offload feature. Action None.
DYNA1065E: The operation "{0}" for cacheName "{1}" cannot be performed because cache provider "{2}" does not support the DRS replication feature.
Explanation This specific operation cannot be performed because cache provider does not support the date replication service (DRS) replication feature. Action None.
DYNA1066E: Unable to initialize the cache provider "{0}". The Dynamic cache will be used to create the cache instance "{1}" instead of the configured cache provider.
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.
DYNA1067E: The cache size in MB feature is disabled because the cached object is not sizable. ClassName={0} Type={1}
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.
DYNA1068E: The cache size in MB feature is disabled because the configured cache provider "{0}" does not support this feature for the cache instance "{1}".
Explanation The cache size in MB feature is disabled because the configured cache provider does not support this feature. Action None
DYNA1069I: The "lruToDiskTriggerTime" custom property will be set to "{0}" for getting better performance.
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
DYNA1070I: Cache instance "{0}" is full and has reached the maximum configured size of {1} entries. Space on the JVM heap for new entries will now be made by evicting existing cache entries using the LRU algorithm. Please consider enabling the disk offload feature for the cache instance to prevent the discard of cache entries from memory.
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.
DYNA1071I: The cache provider "{0}" is being used.
Explanation This shows the name of cache provider being used. Action None.
DYNA1072W: The cache id "{0}" will not be replicated to other servers because "skipMemoryWriteToDisk" is set to true. The sharing policy will be set to "not-shared".
Explanation The specified cache id will not be replicated to other servers because skipMemoryWriteToDisk is set to true. Action None.
DYNA1073E: The "RemoteJMSInvalidator" external cache group is not configured correctly. The following address was provided for the external cache group member: "{0}"
Explanation We must resolve the configuration error for the specified external cache group to function correctly. Action None.
DYNA1074W: The "RemoteJMSInvalidator" external cache group is no longer connected. The configured JNDI name of the queue connection factory is "{0}" and the JNDI name of the targeted destination is "{1}".
Explanation The service integration bus servers in the specified queue connection factory are no longer available. Action None.
DYNA1075I: The "RemoteJMSInvalidator" external cache group is connected. The configured JNDI name of the queue connection factory is "{0}" and the JNDI name of the targeted destination is "{1}".
Explanation The external cache group is now connected to the service integration bus servers that are defined in the queue connection factory. Action None.
DYNA1076W: The "RemoteJMSInvalidator" external cache group is unable to connect. The configured JNDI name of the queue connection factory is "{0}" and the JNDI name of the targeted destination is "{1}".
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.
DYNA1077I: The custom property with the name, "{0}", and the value, "{1}", has been detected.
Explanation The name and value of a defined custom property. Action None.
DYNA1080I: OpenJPA L2 QueryCache Dynacache instance "{0}" created or retrieved successfully for persistent unit "{1}".
Explanation OpenJPA L2 QueryCache Dynacache instance created successfully. Action None.
DYNA1081I: OpenJPA L2 DataCache Dynacache instance "{0}" created or retrieved successfully for persistent unit "{1}".
Explanation OpenJPA L2 DataCache Dynacache instance created successfully. Action None.
DYNA1082W: Replication Domain has not been specified.
Explanation Forcing enableCacheReplication to false. Action Please configure a WebSphere Replication domain to associate with the cache instance.
DYNA1083W: No named cache is specified for the open-jpa L2 cache instance. Using the name of the persistent unit "{0}" as the cache instance name.
Explanation None. Action Please configure a name for the open-jpa L2 cache instance.
DYNA1084W: No cache size is specified for the open-jpa L2 cache instance "{0}". Setting the cache size in memory to "{1}".
Explanation None. Action Please configure a size for the open-jpa L2 cache instance.
DYNA1085W: "{0}" property has been configured to incompatible value "{1}". Forcing this value to "{2}".
Explanation None. Action Please provide a consistent configuration to the open-jpa L2 cache instance.
DYNA1086I: Since the openjpa.DataCacheManager property is set to "dynacache" the Dynacache OpenJPA L2 Cache Provider will FORCE set the openjpa.DataCache property to "dynacache".
Explanation This message is for informational purposes only. Action No action is required.
DYNA1087I: Since the openjpa.DataCacheManager property is set to "dynacache" the Dynacache OpenJPA L2 Cache Provider will FORCE set the openjpa.RemoteCommitProvider property to "none".
Explanation This message is for informational purposes only. Action No action is required.
DYNA1088I: Since the openjpa.Datacache property is set to "dynacache" the Dynacache OpenJPA L2 Cache Provider will FORCE set openjpa.RemoteCommitProvider property to "none".
Explanation This message is for informational purposes only. Action No action is required.
DYNA1089I: Since the openjpa.Querycache property is set to "dynacache" the Dynacache OpenJPA L2 Cache Provider will FORCE set the "openjpa.DataCache property to "dynacache" .
Explanation This message is for informational purposes only. Action No action is required.
DYNA1090I: Dynamic Cache service is disabled.
Explanation The Dynamic Cache, Object cache and Servlet caching services have been disabled through the administrative console or scripting. Action Enable the Dynamic Cache service by setting the "enable" attribute of the server scoped "DynamicCache" AdminConfig object or through the administrative console panel Application servers > <server_name gt; > Dynamic cache service
DYNA1091E: Configuration for cache instance "{0}", was not recognized due to exception "{0}".
Explanation The Dynamic Cache configuration for cache instance is invalid because of the thrown exception. Action Please correct and address at the cause of the exception so that the cache configuration can be successfully added to the Dynamic Cache runtime.
DYNA1092E: No DataCache with name "{0}" exists.
Explanation Please confirm that the L2 DataCache was created successfully. Action Please confirm that the L2 Data Cache is correct.
DYNA1093E: DataCache "{0}" not configure with the correct DataCacheManager in persistent unit "{1}" .
Explanation "openjpa.DataCacheManager" property should be set to "dynacache". Action Please correct this property in the persistence.xml.
DYNA1094E: Entity Class "{0}" could NOT be loaded by classloader "{1}".
Explanation Please confirm that Class does exist in the application and is visible to the application server classloader. Action Please provide the correct Entity Class name and configured a sever scoped shared library containing the classes associated with the server.
DYNA1095E: Persistence-unit: "{0}" not found in application: "{1}" module: "{2}" .
Explanation Persistence unit xml could not located in the specified location. Action Please confirm that the persistence unit is indeed placed in the location specified by the mbean parameters.