<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/css" href="../../resources/stylesheets/wasmsgxml.css"?>
<TMSSource name="TivoliMessages" tmsVersion="1.0" xml:lang="en">
<!-- CMVC MSG File Name = SERV1/ws/code/dynacache/src/com/ibm/ws/cache/resources/dynacache.nlsprops -->
<!-- DO NOT EDIT THIS FILE - This file was generated by the XML/Html & Property emitter -->
<!-- BEGIN MESSAGES -->
<Message ID="DYNA0048I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA0048I" varFormat="Java">
    DYNA0048I=DYNA0048I: WebSphere Dynamic Cache initialized successfully.
  </MsgText>
  <Explanation>
    The dynamic cache services successfully initialized.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1050E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1050E" varFormat="Java">
    DYNA1050E=DYNA1050E: Exception occurred while trying to invoke MBean command &quot;{0}&quot; in the server &quot;{1}&quot;. Exception: {2}
  </MsgText>
  <Explanation>
    Exception occurred while trying to invoke MBean command.
  </Explanation>
  <UserResponse>
    Find the explanation of the exception in the server SystemOut.log file.
  </UserResponse>
</Message>
<Message ID="DYNA1046E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1046E" varFormat="Java">
    DYNA1046E=DYNA1046E: The input server &quot;{0}&quot; is not a valid server name.
  </MsgText>
  <Explanation>
    The input server name is not valid.
  </Explanation>
  <UserResponse>
    Ensure that the server exists and the name is correct.
  </UserResponse>
</Message>
<Message ID="DYNA1010E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1010E" varFormat="Java">
    DYNA1010E=DYNA1010E: Method {0}: Parameter error: entryKey is null.
  </MsgText>
  <Explanation>
    The specified method was passed a null entryKey parameter.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1006E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1006E" varFormat="Java">
    DYNA1006E=DYNA1006E: Method {0} caught exception: {1}
  </MsgText>
  <Explanation>
    An exception was caught in the specified method.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0051E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0051E" varFormat="Java">
    DYNA0051E=DYNA0051E: Could not cache a CacheableCommand because WebSphere Dynamic Caching is disabled.
  </MsgText>
  <Explanation>
    An attempt was made to use a CacheableCommand, but the servlet caching in the Web container settings is disabled.
  </Explanation>
  <UserResponse>
    Enable the servlet caching in the Web container settings from the administrative console.
  </UserResponse>
</Message>
<Message ID="DYNA0047I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA0047I" varFormat="Java">
    DYNA0047I=DYNA0047I: Successfully loaded cache-entries from cache configuration file {0}.
  </MsgText>
  <Explanation>
    A cache configuration file was successfully processed for cache entries from the specified location.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0014I" severity="I" prefix="yes">
  <MsgText pgmKey="dynacache.uriMatched" varFormat="Java">
    dynacache.uriMatched=DYNA0014I: {0} is a cacheable URI
  </MsgText>
  <Explanation>
    A servlet or JSP file initialized that has a valid cache policy configured.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0006E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.externalnotfound" varFormat="Java">
    dynacache.externalnotfound=DYNA0006E: ExternalCacheGroup {0} was not found.
  </MsgText>
  <Explanation>
    The external cache group to which this servlet output should be forwarded was not registered in the global cache configuration.
  </Explanation>
  <UserResponse>
    Check the spelling of this external cache group. If correct, define this group in the global cache properties.
  </UserResponse>
</Message>
<Message ID="DYNA1045E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1045E" varFormat="Java">
    DYNA1045E=DYNA1045E: The input node &quot;{0}&quot; is not a valid node name.
  </MsgText>
  <Explanation>
    The input node name is not valid.
  </Explanation>
  <UserResponse>
    Ensure that the node exists and the name is correct.
  </UserResponse>
</Message>
<Message ID="DYNA1095E" severity="E" prefix="yes">
  <MsgText pgmKey="unable-to-retrieve-OpenJPA-configuration-for-cache-instance" varFormat="Java">
    unable-to-retrieve-OpenJPA-configuration-for-cache-instance=DYNA1095E: Persistence-unit: &quot;{0}&quot; not found in application: &quot;{1}&quot; module: &quot;{2}&quot; .
  </MsgText>
  <Explanation>
    Persistence unit xml could not located in the specified location.
  </Explanation>
  <UserResponse>
    Please confirm that the persistence unit is indeed placed in the location specified by the mbean parameters.
  </UserResponse>
</Message>
<Message ID="DYNA1005E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1005E" varFormat="Java">
    DYNA1005E=DYNA1005E: WebSphere Dynamic Cache instance named {0} can not be accessed because it is the wrong type.
  </MsgText>
  <Explanation>
    The named dynamic cache instance cannot be used.  Dynamic caching is disabled for the named instance.
  </Explanation>
  <UserResponse>
    Use the administrative console to configure the cache instance resource using the correct type.
  </UserResponse>
</Message>
<Message ID="DYNA0018E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.idgeneratorerror" varFormat="Java">
    dynacache.idgeneratorerror=DYNA0018E: Error loading ID Generator {0}
  </MsgText>
  <Explanation>
    Error loading ID Generator.
  </Explanation>
  <UserResponse>
    Debug the problem using the provided error message.
  </UserResponse>
</Message>
<Message ID="DYNA0050E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0050E" varFormat="Java">
    DYNA0050E=DYNA0050E: Unrecognized value {0} for element {1}.
  </MsgText>
  <Explanation>
    The specified element in the cache configuration file contained an unrecognized value.
  </Explanation>
  <UserResponse>
    Consult the product documentation for information on valid values for the specified element.
  </UserResponse>
</Message>
<Message ID="DYNA0046E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0046E" varFormat="Java">
    DYNA0046E=DYNA0046E: I/O exception {0} occurred while processing configuration file {1}.
  </MsgText>
  <Explanation>
    An error occurred while reading the cache configuration file.
  </Explanation>
  <UserResponse>
    Correct the problem that is specified in the message.
  </UserResponse>
</Message>
<Message ID="DYNA1044E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1044E" varFormat="Java">
    DYNA1044E=DYNA1044E: Internal error: Failure to create the MessageDigest for MD5 algorithm. Exception: {0}
  </MsgText>
  <Explanation>
    Internal error: Failure to create the MessageDigest for MD5 algorithm.
  </Explanation>
  <UserResponse>
    Contact IBM service for debugging this problem.
  </UserResponse>
</Message>
<Message ID="DYNA1004E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1004E" varFormat="Java">
    DYNA1004E=DYNA1004E: WebSphere Dynamic Cache instance named {0} can not be initialized because it is not configured.
  </MsgText>
  <Explanation>
    The named dynamic cache instance cannot be initialized.  Dynamic caching is disabled for the named instance.
  </Explanation>
  <UserResponse>
    Use the administrative console to configure the cache instance resource.
  </UserResponse>
</Message>
<Message ID="DYNA0008E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.notexist" varFormat="Java">
    dynacache.notexist=DYNA0008E: CacheUnit no longer exists.
  </MsgText>
  <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.
  </Explanation>
  <UserResponse>
    Verify that the specified cache unit should be active; if so, restart the server.
  </UserResponse>
</Message>
<Message ID="DYNA0045E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0045E" varFormat="Java">
    DYNA0045E=DYNA0045E: XML parsing error: {0}, while parsing file {1} at line {2}, column {3}.
  </MsgText>
  <Explanation>
    An XML parsing warning occurred while processing a cache configuration file.
  </Explanation>
  <UserResponse>
    Correct the problem that is specified in the message.
  </UserResponse>
</Message>
<Message ID="DYNA1043E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1043E" varFormat="Java">
    DYNA1043E=DYNA1043E: The input pattern &quot;{0}&quot; is not a valid regular expression. Exception: {1}
  </MsgText>
  <Explanation>
    The input pattern is not a valid regular expression.
  </Explanation>
  <UserResponse>
    Check the java.util.regex.Pattern class.
  </UserResponse>
</Message>
<Message ID="DYNA1039I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1039I" varFormat="Java">
    DYNA1039I=DYNA1039I: Total number of cache entries in the disk cache is {0} for cache name &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    Displays the total number of entries in the disk cache.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1003E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1003E" varFormat="Java">
    DYNA1003E=DYNA1003E: WebSphere Dynamic Cache instance named {0} can not be initialized because of error {1}.
  </MsgText>
  <Explanation>
    The named dynamic cache instance cannot be initialized.  The named instance is not avaliable.
  </Explanation>
  <UserResponse>
    Debug the problem using the error message.  The application server logs contain additional information.
  </UserResponse>
</Message>
<Message ID="DYNA0044E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0044E" varFormat="Java">
    DYNA0044E=DYNA0044E: XML parsing warning: {0}, while parsing file {1} at line {2}, column {3}.
  </MsgText>
  <Explanation>
    An XML parsing warning occurred while processing a cache configuration file.
  </Explanation>
  <UserResponse>
    Correct the problem that is specified in the message.
  </UserResponse>
</Message>
<Message ID="DYNA0022E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.configerror" varFormat="Java">
    dynacache.configerror=DYNA0022E: Error processing dynamic cache configuration: {0}
  </MsgText>
  <Explanation>
    Unanticipated error processing cache configuration.
  </Explanation>
  <UserResponse>
    Debug the problem using the provided error message.
  </UserResponse>
</Message>
<Message ID="DYNA1042E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1042E" varFormat="Java">
    DYNA1042E=DYNA1042E: The input cache instance &quot;{0}&quot; is not valid or is not configured.
  </MsgText>
  <Explanation>
    The input cache instance is not valid. Configure the cache instance by using either the administrative console or the cacheinstances.properties file.
  </Explanation>
  <UserResponse>
    Ensure that a cache instance is configured correctly and the name of the cache instance is correct.
  </UserResponse>
</Message>
<Message ID="DYNA1038I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1038I" varFormat="Java">
    DYNA1038I=DYNA1038I: Total number of cache entries in the memory cache is {0} for cache name &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    Displays the total number of entries in the memory cache.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1002E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1002E" varFormat="Java">
    DYNA1002E=DYNA1002E: WebSphere Dynamic Cache instances can not be initialized because of error {0}.
  </MsgText>
  <Explanation>
    The dynamic cache instances cannot be initialized.  No caches instances are avaliable.
  </Explanation>
  <UserResponse>
    Debug the problem using the error message.  The application server logs contain additional information.
  </UserResponse>
</Message>
<Message ID="DYNA1041W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA1041W" varFormat="Java">
    DYNA1041W=DYNA1041W: Cache comparsion between server1 &quot;{0}&quot; and server2 &quot;{1}&quot; for cache name &quot;{2}&quot; failed.
  </MsgText>
  <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.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0043E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0043E" varFormat="Java">
    DYNA0043E=DYNA0043E: Configuration file {0} contained errors and will not be used.
  </MsgText>
  <Explanation>
    The specified configuration file contained critical errors and cannot be utilized.
  </Explanation>
  <UserResponse>
    Correct the specified errors in the configuration file.
  </UserResponse>
</Message>
<Message ID="DYNA1077I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1077I" varFormat="Java">
    DYNA1077I=DYNA1077I: The custom property with the name, &quot;{0}&quot;, and the value, &quot;{1}&quot;, has been detected.
  </MsgText>
  <Explanation>
    The name and value of a defined custom property.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0039E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0039E" varFormat="Java">
    DYNA0039E=DYNA0039E: Commands do not support custom metadata generating classes.  You must override the prepareMetaData() method.
  </MsgText>
  <Explanation>
    The cache configuration file specified a custom metadata generator for a command, but this is not supported.
  </Explanation>
  <UserResponse>
    See the product documentation for information on implementing the CacheableCommand.prepareMetaData method.
  </UserResponse>
</Message>
<Message ID="DYNA1037I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1037I" varFormat="Java">
    DYNA1037I=DYNA1037I: List of {0} cache keys and their hashcodes in the PushPullTable for cache name &quot;{1}&quot;: {2}
  </MsgText>
  <Explanation>
    Displays each cache key and its hashcode in the PushPullTable.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1001I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1001I" varFormat="Java">
    DYNA1001I=DYNA1001I: WebSphere Dynamic Cache instance named {0} initialized successfully.
  </MsgText>
  <Explanation>
    The named Dynamic Cache instance was successfully initialized.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1076W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA1076W" varFormat="Java">
    DYNA1076W=DYNA1076W: The &quot;RemoteJMSInvalidator&quot; external cache group is unable to connect. The configured JNDI name of the queue connection factory is &quot;{0}&quot; and the JNDI name of the targeted destination is &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    The external cache group is unable to connect to the service integration bus servers that are defined in the queue connection factory.
  </Explanation>
  <UserResponse>
    You may need to restart the targeted service integration bus servers.
  </UserResponse>
</Message>
<Message ID="DYNA0042E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0042E" varFormat="Java">
    DYNA0042E=DYNA0042E: Invalid component type {0} for servlet/jsp fragment {1}.
  </MsgText>
  <Explanation>
    An unsupported component type was encountered while processing the specified servlet or JSP file.
  </Explanation>
  <UserResponse>
    Correct the cache configuration policy to contain only valid component types for the specified object.
  </UserResponse>
</Message>
<Message ID="DYNA1040I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1040I" varFormat="Java">
    DYNA1040I=DYNA1040I: Total number of cache IDs in the PushPullTable is {0} for cache name &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    Displays the total number of cache IDs in the PushPullTable.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0038E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0038E" varFormat="Java">
    DYNA0038E=DYNA0038E: Unrecognized component type {0} for command {1}.
  </MsgText>
  <Explanation>
    The specified component type is not valid for command caching.
  </Explanation>
  <UserResponse>
    Valid component types for commands are &quot;method&quot; and &quot;field&quot;.
  </UserResponse>
</Message>
<Message ID="DYNA1036I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1036I" varFormat="Java">
    DYNA1036I=DYNA1036I: List of {0} cache keys and their hashcodes in the disk cache for cache name &quot;{1}&quot;: {2}
  </MsgText>
  <Explanation>
    Displays each cache key and its hashcode in the disk cache.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0005E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.externaldup" varFormat="Java">
    dynacache.externaldup=DYNA0005E: Duplicate ExternalCacheGroup entry for address {0}.
  </MsgText>
  <Explanation>
    A duplicate ExternalCacheGroup was entered in the configuration.
  </Explanation>
  <UserResponse>
    Remove the duplicate group.
  </UserResponse>
</Message>
<Message ID="DYNA0025E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.badexternalconfig" varFormat="Java">
    dynacache.badexternalconfig=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.
  </MsgText>
  <Explanation>
    An entry was marked as externally cacheable and containes additional ID generation rules.
  </Explanation>
  <UserResponse>
    Remove the additional rules.
  </UserResponse>
</Message>
<Message ID="DYNA0041E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0041E" varFormat="Java">
    DYNA0041E=DYNA0041E: Invalid component type {0} for edgeable fragment {1}.
  </MsgText>
  <Explanation>
    A servlet or JSP was marked Edgeable, but the cache policy contains component rules which are not valid on an IBM Edge Server.
  </Explanation>
  <UserResponse>
    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.
  </UserResponse>
</Message>
<Message ID="DYNA1075I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1075I" varFormat="Java">
    DYNA1075I=DYNA1075I: The &quot;RemoteJMSInvalidator&quot; external cache group is connected. The configured JNDI name of the queue connection factory is &quot;{0}&quot; and the JNDI name of the targeted destination is &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    The external cache group is now connected to the service integration bus servers that are defined in the queue connection factory.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0037E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0037E" varFormat="Java">
    DYNA0037E=DYNA0037E: Unrecognized element {0} while processing element {1}.
  </MsgText>
  <Explanation>
    An unrecognized element was encountered while parsing the cache configuration file.
  </Explanation>
  <UserResponse>
    Correct the document to match the cachespec.dtd file.
  </UserResponse>
</Message>
<Message ID="DYNA1035I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1035I" varFormat="Java">
    DYNA1035I=DYNA1035I: List of {0} cache keys and their hashcodes in the memory cache for cache name &quot;{1}&quot;: {2}
  </MsgText>
  <Explanation>
    Displays each cache key and its hashcode in the memory cache.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0003E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.badconfig" varFormat="Java">
    dynacache.badconfig=DYNA0003E: Not caching {0} due to misconfiguration.
  </MsgText>
  <Explanation>
    The servlet specified was incorrectly configured.
  </Explanation>
  <UserResponse>
    Check that legal, non-contradictory values have been given, and that all required fields are specified.
  </UserResponse>
</Message>
<Message ID="DYNA1074W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA1074W" varFormat="Java">
    DYNA1074W=DYNA1074W: The &quot;RemoteJMSInvalidator&quot; external cache group is no longer connected. The configured JNDI name of the queue connection factory is &quot;{0}&quot; and the JNDI name of the targeted destination is &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    The service integration bus servers in the specified queue connection factory are no longer available.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1082W" severity="W" prefix="yes">
  <MsgText pgmKey="specify-replication-domain" varFormat="Java">
    specify-replication-domain=DYNA1082W: Replication Domain has not been specified.
  </MsgText>
  <Explanation>
    Forcing enableCacheReplication to false.
  </Explanation>
  <UserResponse>
    Please configure a WebSphere Replication domain to associate with the cache instance.
  </UserResponse>
</Message>
<Message ID="DYNA1034W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA1034W" varFormat="Java">
    DYNA1034W=DYNA1034W: Custom property &quot;disableTemplatesSupport&quot; is set to {0} which does not match with the current state of disk files for cache name &quot;{1}&quot;. The custom property &quot;disableTemplatesSupport&quot; is set to {2}.
  </MsgText>
  <Explanation>
    The setting of custom property &quot;disableTemplatesSupport&quot; does not match the current state of disk files.
  </Explanation>
  <UserResponse>
    To set custom property &quot;disableTemplatesSupport&quot; to your desired settings, delete all disk cache files and restart the server.
  </UserResponse>
</Message>
<Message ID="DYNA0040E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0040E" varFormat="Java">
    DYNA0040E=DYNA0040E: Illegal component type {0} servicing {1}.
  </MsgText>
  <Explanation>
    An unsupported component type was encountered while processing the specified object.
  </Explanation>
  <UserResponse>
    Correct the cache configuration policy to contain only valid component types for the specified object.
  </UserResponse>
</Message>
<Message ID="DYNA0036E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0036E" varFormat="Java">
    DYNA0036E=DYNA0036E: Exception retrieving field {0} from class {1}.  Exception: {2}
  </MsgText>
  <Explanation>
    An error occurred while retrieving the specified field to generate a cache ID.
  </Explanation>
  <UserResponse>
    Debug the problem using the information that is provided in the error message.
  </UserResponse>
</Message>
<Message ID="DYNA1033W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA1033W" varFormat="Java">
    DYNA1033W=DYNA1033W: Custom property &quot;disableDependencyId&quot; is set to {0} which does not match with the current state of disk files for cache name &quot;{1}&quot;. The custom property &quot;disableDependencyId&quot; is set to {2}.
  </MsgText>
  <Explanation>
    The setting of custom property &quot;disableDependencyId&quot; does not match the current state of disk files.
  </Explanation>
  <UserResponse>
    To set custom property &quot;disableDependencyId&quot; to your desired settings, delete all disk cache files and restart the server.
  </UserResponse>
</Message>
<Message ID="DYNA1073E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1073E" varFormat="Java">
    DYNA1073E=DYNA1073E: The &quot;RemoteJMSInvalidator&quot; external cache group is not configured correctly. The following address was provided for the external cache group member: &quot;{0}&quot;
  </MsgText>
  <Explanation>
    You must resolve the configuration error for the specified external cache group to function correctly.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0035E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0035E" varFormat="Java">
    DYNA0035E=DYNA0035E: Unable to introspect field {0} from class {1}.  Exception: {2}
  </MsgText>
  <Explanation>
    An error occurred while trying to locate the field as specified in the cache configuration file.
  </Explanation>
  <UserResponse>
    Verify that the field specified in the cache configuration file exists in the object being invoked and the field is public.
  </UserResponse>
</Message>
<Message ID="DYNA1069I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1069I" varFormat="Java">
    DYNA1069I=DYNA1069I: The &quot;lruToDiskTriggerTime&quot; custom property will be set to &quot;{0}&quot; for getting better performance.
  </MsgText>
  <Explanation>
    Since memory cache size in MB or LRU trigger percent feature is enabled, the &quot;lruToDiskTriggerTime&quot; custom property will be changed to better value in order to get better performance.
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<Message ID="DYNA1072W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA1072W" varFormat="Java">
    DYNA1072W=DYNA1072W: The cache id &quot;{0}&quot; will not be replicated to other servers because &quot;skipMemoryWriteToDisk&quot; is set to true. The sharing policy will be set to &quot;not-shared&quot;.
  </MsgText>
  <Explanation>
    The specified cache id will not be replicated to other servers because skipMemoryWriteToDisk is set to true.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1029I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1029I" varFormat="Java">
    DYNA1029I=DYNA1029I: DynacacheDRSController DRS Instance {0} received event NOT_CONGESTED.
  </MsgText>
  <Explanation>
    The specified DynacacheDRSController DRS Instance received event NOT_CONGESTED.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0034E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0034E" varFormat="Java">
    DYNA0034E=DYNA0034E: Exception invoking method {0} on class {1}.  Exception: {2}
  </MsgText>
  <Explanation>
    An error occurred while invoking the specified method to generate a cache ID.
  </Explanation>
  <UserResponse>
    Debug the problem using the information that is provided in the error message.
  </UserResponse>
</Message>
<Message ID="DYNA1068E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1068E" varFormat="Java">
    DYNA1068E=DYNA1068E: The cache size in MB feature is disabled because the configured cache provider &quot;{0}&quot; does not support this feature for the cache instance &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    The cache size in MB feature is disabled because the configured cache provider does not support this feature.
  </Explanation>
  <UserResponse>
    None
  </UserResponse>
</Message>
<Message ID="DYNA1032E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1032E" varFormat="Java">
    DYNA1032E=DYNA1032E: Property with name &quot;primary-storage&quot; must be set to either the value &quot;memory&quot; or &quot;disk&quot;.  Value present: {0}.
  </MsgText>
  <Explanation>
    The specified element must have a value of either memory or disk, but another value was specified.
  </Explanation>
  <UserResponse>
    Correct the element to have the value &quot;memory&quot; or &quot;disk&quot;.
  </UserResponse>
</Message>
<Message ID="DYNA0069W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA0069W" varFormat="Java">
    DYNA0069W=DYNA0069W: An invalid value &quot;{0}&quot; for custom property &quot;{1}&quot; in cache name &quot;{2}&quot;. The valid range is low: &quot;{3}&quot; and high: &quot;{4}&quot;. This custom property is set to &quot;{5}&quot;.
  </MsgText>
  <Explanation>
    The value for custom property is not valid. Correct the value using the range-specified low and high values in the warning message.
  </Explanation>
  <UserResponse>
    Correct the value using the range-specified low and high values in the warning message.
  </UserResponse>
</Message>
<Message ID="DYNA1028I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1028I" varFormat="Java">
    DYNA1028I=DYNA1028I: DynacacheDRSController DRS Instance {0} received event IS_CONGESTED.
  </MsgText>
  <Explanation>
    The specified DynacacheDRSController DRS Instance received event IS_CONGESTED.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0073I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA0073I" varFormat="Java">
    DYNA0073I=DYNA0073I: Flush to disk on stop for cache name &quot;{0}&quot; has completed. The statistics are: {1}
  </MsgText>
  <Explanation>
    The flush to disk on stop operation has completed with the statistics.
  </Explanation>
  <UserResponse>
    No user action is required.
  </UserResponse>
</Message>
<Message ID="DYNA1071I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1071I" varFormat="Java">
    DYNA1071I=DYNA1071I: The cache provider &quot;{0}&quot; is being used.
  </MsgText>
  <Explanation>
    This shows the name of cache provider being used.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0033E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0033E" varFormat="Java">
    DYNA0033E=DYNA0033E: Unable to introspect method {0} from class {1}.  Exception: {2}
  </MsgText>
  <Explanation>
    An error occurred while trying to locate the method as specified in the cache configuration file.
  </Explanation>
  <UserResponse>
    Verify that the specified method in the cache configuration file exists in the object being invoked and that the method is public.
  </UserResponse>
</Message>
<Message ID="DYNA1067E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1067E" varFormat="Java">
    DYNA1067E=DYNA1067E: The cache size in MB feature is disabled because the cached object is not sizable.  ClassName={0}   Type={1}
  </MsgText>
  <Explanation>
    The cache size in MB feature is disabled because the cached object is not implemented to be sizable.
  </Explanation>
  <UserResponse>
    Ensure that the cached object class implements com.ibm.websphere.cache.Sizable interface.
  </UserResponse>
</Message>
<Message ID="DYNA0029E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0029E" varFormat="Java">
    DYNA0029E=DYNA0029E: Illegal use of idgenerator {0} when component {1} is already defined.
  </MsgText>
  <Explanation>
    A cache policy specified both a component and idgenerator for the same cache ID rule.
  </Explanation>
  <UserResponse>
    Use either component tags or an idgenerator, but not both simultaneously.
  </UserResponse>
</Message>
<Message ID="DYNA1031E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1031E" varFormat="Java">
    DYNA1031E=DYNA1031E: Invalid range, low atribute: {0} is greater than high attribute: {1}.
  </MsgText>
  <Explanation>
    The low and high attribute values specified for the range are not valid.
  </Explanation>
  <UserResponse>
    Correct the the low and high attributes values such that the low value is less than the high value.
  </UserResponse>
</Message>
<Message ID="DYNA0068W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA0068W" varFormat="Java">
    DYNA0068W=DYNA0068W: Invalid disk threshold set for cache name &quot;{0}&quot;. Using default values of 80% and 70% for high and low threshold limits respectively.
  </MsgText>
  <Explanation>
    The disk cache threshold limit has either been set &lt; 0 or high threshold is lower than low threshold limit.
  </Explanation>
  <UserResponse>
    The disk cache threshold should be greater than 0 and high threshold limit should be greater than low threshold limit.
  </UserResponse>
</Message>
<Message ID="DYNA1027I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1027I" varFormat="Java">
    DYNA1027I=DYNA1027I: DynacacheDRSController DRS Instance {0} received event REPLICATION_DOWN.
  </MsgText>
  <Explanation>
    The specified DynacacheDRSController DRS Instance received event REPLICATION_DOWN.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1083W" severity="W" prefix="yes">
  <MsgText pgmKey="no-cache-name" varFormat="Java">
    no-cache-name=DYNA1083W: No named cache is specified for the open-jpa L2 cache  instance. Using the name of the persistent unit &quot;{0}&quot; as the cache instance name.
  </MsgText>
  <Explanation>
    None.
  </Explanation>
  <UserResponse>
    Please configure a name for the open-jpa L2 cache instance.
  </UserResponse>
</Message>
<Message ID="DYNA0009E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.xmlnodoc" varFormat="Java">
    dynacache.xmlnodoc=DYNA0009E: No element named {0} in document {1}.
  </MsgText>
  <Explanation>
    When parsing the specified document, an expected XML element was not found.
  </Explanation>
  <UserResponse>
    Compare the XML file format to the product documentation, looking for a misconfiguration.
  </UserResponse>
</Message>
<Message ID="DYNA0072E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0072E" varFormat="Java">
    DYNA0072E=DYNA0072E: Offload to disk is disabled for cache name &quot;{0}&quot; because a disk exception has occurred. The disk offload location is in &quot;{1}&quot;. Exception: &quot;{2}&quot;.
  </MsgText>
  <Explanation>
    The disk offload feature is disabled for the specified cache name because a disk exception has occurred.
  </Explanation>
  <UserResponse>
    The disk cache files for this cache instance will be deleted when the server is restarted.
  </UserResponse>
</Message>
<Message ID="DYNA1070I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1070I" varFormat="Java">
    DYNA1070I=DYNA1070I: Cache instance &quot;{0}&quot; 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.
  </MsgText>
  <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.
  </Explanation>
  <UserResponse>
    Enable the disk offload feature for the cache instance to prevent the discard of cache entries from memory.
  </UserResponse>
</Message>
<Message ID="DYNA0032E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0032E" varFormat="Java">
    DYNA0032E=DYNA0032E: Element or attribute &quot;{0}&quot; must be set to either the value &quot;true&quot; or &quot;false&quot;.  Value present: {0}.
  </MsgText>
  <Explanation>
    The specified element must have a value of either true or false, but another value was specified.
  </Explanation>
  <UserResponse>
    Correct the element to have a &quot;true&quot; or &quot;false&quot; value.
  </UserResponse>
</Message>
<Message ID="DYNA1081I" severity="I" prefix="yes">
  <MsgText pgmKey="dataCache-instance-created" varFormat="Java">
    dataCache-instance-created=DYNA1081I: OpenJPA L2 DataCache Dynacache instance &quot;{0}&quot; created or retrieved successfully for persistent unit &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    OpenJPA L2 DataCache Dynacache instance created successfully.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0071W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA0071W" varFormat="Java">
    DYNA0071W=DYNA0071W: The custom property &quot;diskCacheSizeInGB&quot; for cache name &quot;{0}&quot; is set to a larger value &quot;{1}&quot; because total disk cache files size has a larger value. To set &quot;diskCacheSizeInGB&quot; to a smaller value, delete all disk cache files under the directory &quot;{2}&quot;.
  </MsgText>
  <Explanation>
    The disk cache files cannot shrink.
  </Explanation>
  <UserResponse>
    To set custom property &quot;diskCacheSizeInGB&quot; to a smaller value, delete all disk cache files and restart the server.
  </UserResponse>
</Message>
<Message ID="DYNA1066E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1066E" varFormat="Java">
    DYNA1066E=DYNA1066E: Unable to initialize the cache provider &quot;{0}&quot;. The Dynamic cache will be used to create the cache instance &quot;{1}&quot; instead of the configured cache provider.
  </MsgText>
  <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.
  </Explanation>
  <UserResponse>
    Ensure that the cache provider is provided as an Application Server runtime bundle or as a library in the Application Server lib directory.
  </UserResponse>
</Message>
<Message ID="DYNA0028E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0028E" varFormat="Java">
    DYNA0028E=DYNA0028E: Illegal use of component {0} when idgenerator {1} is already defined.
  </MsgText>
  <Explanation>
    A cache policy specified both a component and idgenerator for the same cache ID rule.
  </Explanation>
  <UserResponse>
    Use either component tags or an idgenerator, but not both simultaneously.
  </UserResponse>
</Message>
<Message ID="DYNA1030E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1030E" varFormat="Java">
    DYNA1030E=DYNA1030E: Invalid range values, low: {0} and high: {1} attributes must be integers
  </MsgText>
  <Explanation>
    A required attribute was missing in the cache configuration.
  </Explanation>
  <UserResponse>
    Add the required attribute to your cache configuration file.
  </UserResponse>
</Message>
<Message ID="DYNA1093E" severity="E" prefix="yes">
  <MsgText pgmKey="no-dynacache-manager-configured" varFormat="Java">
    no-dynacache-manager-configured=DYNA1093E: DataCache &quot;{0}&quot; not configure with the correct DataCacheManager in persistent unit &quot;{1}&quot; .
  </MsgText>
  <Explanation>
    &quot;openjpa.DataCacheManager&quot; property should be set to  &quot;dynacache&quot;.
  </Explanation>
  <UserResponse>
    Please correct this property in the persistence.xml.
  </UserResponse>
</Message>
<Message ID="DYNA0067W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA0067W" varFormat="Java">
    DYNA0067W=DYNA0067W: The disk cache garbage collector is disabled and Eviction Policy is set to &quot;NONE&quot; for the cache name &quot;{0}&quot;. Delete all disk cache files under the directory &quot;{1}&quot; before this feature is enabled.
  </MsgText>
  <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.
  </Explanation>
  <UserResponse>
    Delete all disk cache files and then restart the server.
  </UserResponse>
</Message>
<Message ID="DYNA1026I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1026I" varFormat="Java">
    DYNA1026I=DYNA1026I: DynacacheDRSController DRS Instance {0} received event REPLICATION_UP.
  </MsgText>
  <Explanation>
    The specified DynacacheDRSController DRS Instance received event REPLICATION_UP.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1085W" severity="W" prefix="yes">
  <MsgText pgmKey="incompatible-configuration" varFormat="Java">
    incompatible-configuration=DYNA1085W: &quot;{0}&quot; property has been configured to incompatible value &quot;{1}&quot;. Forcing this value to &quot;{2}&quot;.
  </MsgText>
  <Explanation>
    None.
  </Explanation>
  <UserResponse>
    Please provide a consistent configuration to the open-jpa L2 cache instance.
  </UserResponse>
</Message>
<Message ID="DYNA0007E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.externaladaptererror" varFormat="Java">
    dynacache.externaladaptererror=DYNA0007E: Error initializing external cache adapter: {0}
  </MsgText>
  <Explanation>
    The specified error was created during the external cache adapter initialization.
  </Explanation>
  <UserResponse>
    Identify the cause of the error from the error-specific information that is provided in the message
  </UserResponse>
</Message>
<Message ID="DYNA0004E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.questionconfig" varFormat="Java">
    dynacache.questionconfig=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.
  </MsgText>
  <Explanation>
    A servlet was configured with trivial configuration information. This is legal, though unlikely correct, except for the simplest cases.
  </Explanation>
  <UserResponse>
    Verify that the servlet to be cached requires only the invocation URI to determine uniqueness.
  </UserResponse>
</Message>
<Message ID="DYNA0015I" severity="I" prefix="yes">
  <MsgText pgmKey="dynacache.error" varFormat="Java">
    dynacache.error=DYNA0015I: Dynamic Servlet Caching encountered an error: {0}
  </MsgText>
  <Explanation>
    General error message.
  </Explanation>
  <UserResponse>
    Debug the provided error.
  </UserResponse>
</Message>
<Message ID="DYNA0031E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0031E" varFormat="Java">
    DYNA0031E=DYNA0031E: Illegal use of element {0} with id {1}.   Field or method element is already present.
  </MsgText>
  <Explanation>
    The configuration file specified multiple method or field tags for the same component.
  </Explanation>
  <UserResponse>
    Eliminate the duplicate method, field or both elements from the component in the configuration file.
  </UserResponse>
</Message>
<Message ID="DYNA0070W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA0070W" varFormat="Java">
    DYNA0070W=DYNA0070W: The disk cache garbage collector is disabled and Eviction Policy is set to &quot;NONE&quot; for the cache name &quot;{0}&quot;. This is because disk cache size or disk cache in GB limit are not set.
  </MsgText>
  <Explanation>
    It is required to set custom properties &quot;diskCacheSize&quot; or &quot;diskCacheSizeInGB&quot; in order to use the disk cache garbage collector feature.
  </Explanation>
  <UserResponse>
    Set the custom properties &quot;diskCacheSize&quot; or &quot;diskCacheSizeInGB&quot; and restart the server.
  </UserResponse>
</Message>
<Message ID="DYNA1065E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1065E" varFormat="Java">
    DYNA1065E=DYNA1065E: The operation &quot;{0}&quot; for cacheName &quot;{1}&quot; cannot be performed because cache provider &quot;{2}&quot; does not support the DRS replication feature.
  </MsgText>
  <Explanation>
    This specific operation cannot be performed because cache provider does not support the date replication service (DRS) replication feature.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0027E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0027E" varFormat="Java">
    DYNA0027E=DYNA0027E: Unrecognized replication policy: {0}.
  </MsgText>
  <Explanation>
    An unrecognized replication policy was specified.
  </Explanation>
  <UserResponse>
    The valid replication policies are not-shared, shared-push, shared-pull, and shared-push-pull.
  </UserResponse>
</Message>
<Message ID="DYNA0066W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA0066W" varFormat="Java">
    DYNA0066W=DYNA0066W: The feature of limiting disk cache size in GB is disabled for the cache name &quot;{0}&quot;. The custom property &quot;diskCacheSizeInGB&quot; is set to 0. Delete all disk cache files under the directory &quot;{1}&quot; before this feature is enabled.
  </MsgText>
  <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.
  </Explanation>
  <UserResponse>
    Delete all disk cache files and then restart the server.
  </UserResponse>
</Message>
<Message ID="DYNA1025E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1025E" varFormat="Java">
    DYNA1025E=DYNA1025E: Method {0}: Cannot convert the DRSJvmId to bytes - jvmId  = {1}  jvmIdBytes = {2}
  </MsgText>
  <Explanation>
    The specified method is unable to convert the DRSJvmID parameter to a byte array.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0030E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0030E" varFormat="Java">
    DYNA0030E=DYNA0030E: {0} element is missing required attribute &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    A required attribute was missing in the cache configuration.
  </Explanation>
  <UserResponse>
    Add the required attribute to your cache configuration file.
  </UserResponse>
</Message>
<Message ID="DYNA1064E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1064E" varFormat="Java">
    DYNA1064E=DYNA1064E: The operation &quot;{0}&quot; for cacheName &quot;{1}&quot; cannot be performed because cache provider &quot;{2}&quot; does not support the disk cache offload feature.
  </MsgText>
  <Explanation>
    This specific operation cannot be performed because cache provider does not support the disk cache offload feature.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0026E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0026E" varFormat="Java">
    DYNA0026E=DYNA0026E: Error reading element {0}.  While processing value {1}, received exception: {2}.
  </MsgText>
  <Explanation>
    An error occurred while reading the cache configuration file.
  </Explanation>
  <UserResponse>
    Correct the error using the information that is provided in the error message.
  </UserResponse>
</Message>
<Message ID="DYNA0065W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA0065W" varFormat="Java">
    DYNA0065W=DYNA0065W: The disk cache size is over limit {0} for cache name &quot;{1}&quot;.  {2} cache entries were evicted from memory but not offloaded to disk.
  </MsgText>
  <Explanation>
    The cached object will not be offloaded to disk because it is over the disk cache size limit.
  </Explanation>
  <UserResponse>
    Modify the custom property &quot;diskCacheSize&quot; to a larger value so that it can store more caches in the disk.
  </UserResponse>
</Message>
<Message ID="DYNA0016I" severity="I" prefix="yes">
  <MsgText pgmKey="dynacache.stats.dump" varFormat="Java">
    dynacache.stats.dump=DYNA0016I: Dumped dynamic servlet caching statistics to: {0}
  </MsgText>
  <Explanation>
    Cache statistics were written to the specified file.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1024E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1024E" varFormat="Java">
    DYNA1024E=DYNA1024E: Method {0}: Cannot convert the entryKeyList to bytes - entryKeyList = {1}  entryKeyListBytes = {2}
  </MsgText>
  <Explanation>
    The specified method is unable to convert the entryKeyList parameter to a byte array.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0019E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.metadatageneratorerror" varFormat="Java">
    dynacache.metadatageneratorerror=DYNA0019E: Error loading MetaData Generator {0}
  </MsgText>
  <Explanation>
    Error loading MetaData Generator.
  </Explanation>
  <UserResponse>
    Debug the problem using the provided error message.
  </UserResponse>
</Message>
<Message ID="DYNA1059W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA1059W" varFormat="Java">
    DYNA1059W=DYNA1059W: Dynamic Cache instance named {0} cannot be used because the Dynamic Servlet cache service has not been started.
  </MsgText>
  <Explanation>
    The named Dynamic Servlet cache service has not be started. Servlet cache instances cannot be used.
  </Explanation>
  <UserResponse>
    Ensure that Dynamic servlet caching is enabled in the administrative console.
  </UserResponse>
</Message>
<Message ID="DYNA1063E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1063E" varFormat="Java">
    DYNA1063E=DYNA1063E: The operation &quot;{0}&quot; for cacheName &quot;{1}&quot; cannot be performed because cache provider &quot;{2}&quot; does not support the alias feature.
  </MsgText>
  <Explanation>
    This specific operation cannot be performed because cache provider does not support the alias feature.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0064W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA0064W" varFormat="Java">
    DYNA0064W=DYNA0064W: The size of cache entry is over limit {0} MB for cache name &quot;{1}&quot;. {2} cache entries were evicted from memory but not offloaded to disk.
  </MsgText>
  <Explanation>
    The cached object will not be offloaded to disk because it is over the disk cache size in MB limit.
  </Explanation>
  <UserResponse>
    Modify the custom property &quot;diskCacheEntrySizeInMB&quot; to a larger value so that it can store more caches in the disk.
  </UserResponse>
</Message>
<Message ID="DYNA1023E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1023E" varFormat="Java">
    DYNA1023E=DYNA1023E: Method {0}: Parameter error:  entryKeyList is null.
  </MsgText>
  <Explanation>
    The specified method was passed a null for the entryKeyList.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1019E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1019E" varFormat="Java">
    DYNA1019E=DYNA1019E: Method {0}: Parameter error: propKey is null.
  </MsgText>
  <Explanation>
    The specified method was passed a null propKey parameter.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1058W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA1058W" varFormat="Java">
    DYNA1058W=DYNA1058W: Cache replication is disabled for cache instance &quot;{0}&quot; because the Dynamic Cache service is running in a stand-alone server.
  </MsgText>
  <Explanation>
    Cache replication is disabled for cache instance because the Dynamic Cache service is running in a stand-alone server.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1062E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1062E" varFormat="Java">
    DYNA1062E=DYNA1062E: Dynamic Cache (core cache) failed to initialize. Exception: {0}
  </MsgText>
  <Explanation>
    The Dynamic Cache (core cache) failed to initialize.
  </Explanation>
  <UserResponse>
    Debug the problem using the provided error message.
  </UserResponse>
</Message>
<Message ID="DYNA0063W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA0063W" varFormat="Java">
    DYNA0063W=DYNA0063W: The disk cache size has reached the limit {0} GB for cache name &quot;{1}&quot;.  {2} cache entries were evicted from memory but not offloaded to disk.
  </MsgText>
  <Explanation>
    The cached object will not be offloaded to disk because it is over the disk cache size in GB limit.
  </Explanation>
  <UserResponse>
    Modify the custom property &quot;diskCacheSizeInGB&quot; to a larger value so that it can store more caches in the disk.
  </UserResponse>
</Message>
<Message ID="DYNA1022E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1022E" varFormat="Java">
    DYNA1022E=DYNA1022E: Method {0}: Parameter error:  DRSJvmId routing information is null.
  </MsgText>
  <Explanation>
    The specified method was passed a null for the DRSJvmId routing parameter.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1018E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1018E" varFormat="Java">
    DYNA1018E=DYNA1018E: Method {0}: Value tmp returned by proxy.handleBootstrapRequest is null:  tmp = {1}, token = {2}
  </MsgText>
  <Explanation>
    For the specified method the returned value from proxy.handleBootstrapRequest  is null.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1057W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA1057W" varFormat="Java">
    DYNA1057W=DYNA1057W: Cache instance &quot;{0}&quot; defined in the &quot;{1}&quot; is not added because a cache with this name already exists.
  </MsgText>
  <Explanation>
    The cache instance is not added because a cache with this name already exists.
  </Explanation>
  <UserResponse>
    Ensure that the cache instance does not define more than once in the properties files.
  </UserResponse>
</Message>
<Message ID="DYNA0059I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA0059I" varFormat="Java">
    DYNA0059I=DYNA0059I: The disk cache configuration for cache name &quot;{0}&quot;. The configuration is: {1}
  </MsgText>
  <Explanation>
    This shows the disk cache configuration.
  </Explanation>
  <UserResponse>
    No user action is required.
  </UserResponse>
</Message>
<Message ID="DYNA1061E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1061E" varFormat="Java">
    DYNA1061E=DYNA1061E: Neither servlet cache nor object caching is enabled.
  </MsgText>
  <Explanation>
    Neither servlet cache nor object caching is enabled.
  </Explanation>
  <UserResponse>
    Ensure that Dynamic servlet caching is enabled in the administrative console.
  </UserResponse>
</Message>
<Message ID="DYNA1080I" severity="I" prefix="yes">
  <MsgText pgmKey="queryCache-instance-created" varFormat="Java">
    queryCache-instance-created=DYNA1080I: OpenJPA L2 QueryCache Dynacache instance &quot;{0}&quot; created or retrieved successfully for persistent unit &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    OpenJPA L2 QueryCache Dynacache instance created successfully.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1021E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1021E" varFormat="Java">
    DYNA1021E=DYNA1021E: Method {0}: Cannot convert the value parameter to bytes.
  </MsgText>
  <Explanation>
    The specified method is unable to convert the value parameter to bytes.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1084W" severity="W" prefix="yes">
  <MsgText pgmKey="no-cache-size" varFormat="Java">
    no-cache-size=DYNA1084W: No cache size is specified for the open-jpa L2 cache  instance &quot;{0}&quot;.  Setting the cache size in memory to &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    None.
  </Explanation>
  <UserResponse>
    Please configure a size for the open-jpa L2 cache instance.
  </UserResponse>
</Message>
<Message ID="DYNA1060W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA1060W" varFormat="Java">
    DYNA1060W=DYNA1060W: Dynamic Cache instance named {0} cannot be used because the Dynamic Object cache service has not been started.
  </MsgText>
  <Explanation>
    The named Dynamic Object cache service has not be started. Object cache instances cannot be used.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1017E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1017E" varFormat="Java">
    DYNA1017E=DYNA1017E: Method {0}: Parameter error: dbm is null.
  </MsgText>
  <Explanation>
    The specified method was passed a null dbm object.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0062I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA0062I" varFormat="Java">
    DYNA0062I=DYNA0062I: Successfully loaded cache-instances from configuration file {0}.
  </MsgText>
  <Explanation>
    A cache configuration file was successfully processed for cache-instances from the specified location.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0058I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA0058I" varFormat="Java">
    DYNA0058I=DYNA0058I: The disk cache cleanup finished for cache name &quot;{0}&quot;. The statistics are: {1}
  </MsgText>
  <Explanation>
    The disk cache cleanup is finished.
  </Explanation>
  <UserResponse>
    No user action is required.
  </UserResponse>
</Message>
<Message ID="DYNA1056I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1056I" varFormat="Java">
    DYNA1056I=DYNA1056I: Dynamic Cache (object cache) initialized successfully.
  </MsgText>
  <Explanation>
    The Dynamic Cache (object cache) was successfully initialized.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1020E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1020E" varFormat="Java">
    DYNA1020E=DYNA1020E: Method {0}: Parameter error: value is null.
  </MsgText>
  <Explanation>
    The specified method was passed a null for the value parameter.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1016E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1016E" varFormat="Java">
    DYNA1016E=DYNA1016E: Method {0}: dbmBytes is null: dbm = {1}  dbmBytes = {2}
  </MsgText>
  <Explanation>
    The specified method cannot call the proxy because the DRSBootstrapMsg converted to bytes  is null.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0061I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA0061I" varFormat="Java">
    DYNA0061I=DYNA0061I: Flush to disk on stop is disabled for cache name &quot;{0}&quot;.
  </MsgText>
  <Explanation>
    The flush to disk on stop feature is disabled for the specified cache name.
  </Explanation>
  <UserResponse>
    No user action is required.
  </UserResponse>
</Message>
<Message ID="DYNA0013I" severity="I" prefix="yes">
  <MsgText pgmKey="dynacache.cachingDisabled" varFormat="Java">
    dynacache.cachingDisabled=DYNA0013I: Dynamic servlet caching is disabled
  </MsgText>
  <Explanation>
    Dynamic servlet caching is disabled.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0024E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.excludeerror" varFormat="Java">
    dynacache.excludeerror=DYNA0024E: Error building cache policy {0}. &quot;Exclude&quot; variables were duplicates or incorrectly defined for cache variable {1}.
  </MsgText>
  <Explanation>
    Duplicate exclude variables were present.
  </Explanation>
  <UserResponse>
    Remove the duplicate variable or incorrectly-defined exclude variables that were specified.
  </UserResponse>
</Message>
<Message ID="DYNA0057I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA0057I" varFormat="Java">
    DYNA0057I=DYNA0057I: The disk cache cleanup started for the cache name &quot;{0}&quot;. The statistics are: {1}
  </MsgText>
  <Explanation>
    The disk cache cleanup has started to remove expired cache entries.
  </Explanation>
  <UserResponse>
    No user action is required.
  </UserResponse>
</Message>
<Message ID="DYNA1055I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1055I" varFormat="Java">
    DYNA1055I=DYNA1055I: Dynamic Cache (servlet cache) initialized successfully.
  </MsgText>
  <Explanation>
    The Dynamic Cache (servlet cache) was successfully initialized.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0001E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.priority" varFormat="Java">
    dynacache.priority=DYNA0001E: The priority value was not a valid number for entry {0}. Use an integer instead of {1}.
  </MsgText>
  <Explanation>
    The user entered a non-integer or non-positive integer for the priority.
  </Explanation>
  <UserResponse>
    Change the priority value to a positive integer.
  </UserResponse>
</Message>
<Message ID="DYNA0021E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.cacheInitFailed" varFormat="Java">
    dynacache.cacheInitFailed=DYNA0021E: Unable to initialize cache unit {0}: {1}
  </MsgText>
  <Explanation>
    Unanticipated error initializing the cache.
  </Explanation>
  <UserResponse>
    Debug the problem using the provided error message.
  </UserResponse>
</Message>
<Message ID="DYNA0056W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA0056W" varFormat="Java">
    DYNA0056W=DYNA0056W: Disk cache files have been reinitialized because of corrupted data.
  </MsgText>
  <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.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1015E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1015E" varFormat="Java">
    DYNA1015E=DYNA1015E: Method {0}: propKeyBytes is null: propKey = {1}  propKeyBytes = {2}
  </MsgText>
  <Explanation>
    The specified method cannot call the proxy because propKeyBytes is null.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0060I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA0060I" varFormat="Java">
    DYNA0060I=DYNA0060I: Flush to disk on stop is enabled for cache name &quot;{0}&quot;.
  </MsgText>
  <Explanation>
    The flush to disk on stop feature is enabled for the specified cache name.
  </Explanation>
  <UserResponse>
    No user action is required.
  </UserResponse>
</Message>
<Message ID="DYNA0002E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.timeout" varFormat="Java">
    dynacache.timeout=DYNA0002E: The timeout value was not a valid number for entry {0}. Use an integer instead of {1}.
  </MsgText>
  <Explanation>
    The user entered a non-integer for the timeout.
  </Explanation>
  <UserResponse>
    Change the timeout value to a numeral integer.
  </UserResponse>
</Message>
<Message ID="DYNA0010E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.xmlnoelem" varFormat="Java">
    dynacache.xmlnoelem=DYNA0010E: No element named {0} in {1}.
  </MsgText>
  <Explanation>
    When parsing the specified configuration XML files, an expected XML element was not found.
  </Explanation>
  <UserResponse>
    Compare the XML file format to the product documentation, looking for a misconfiguration.
  </UserResponse>
</Message>
<Message ID="DYNA1094E" severity="E" prefix="yes">
  <MsgText pgmKey="incorrect-class-name" varFormat="Java">
    incorrect-class-name=DYNA1094E: Entity Class &quot;{0}&quot; could NOT be loaded by classloader &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    Please confirm that Class does exist in the application and is visible to the application server classloader.
  </Explanation>
  <UserResponse>
    Please provide the correct Entity Class name and configured a sever scoped shared library containing the classes associated with the server.
  </UserResponse>
</Message>
<Message ID="DYNA1054I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1054I" varFormat="Java">
    DYNA1054I=DYNA1054I: Dynamic Cache (core cache) initialized successfully.
  </MsgText>
  <Explanation>
    The Dynamic Cache (core cache) was successfully initialized.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1089I" severity="I" prefix="yes">
  <MsgText pgmKey="incompatible-configuration4" varFormat="Java">
    incompatible-configuration4=DYNA1089I: Since the openjpa.Querycache property is set to  &quot;dynacache&quot; the Dynacache OpenJPA L2 Cache Provider will  FORCE  set the &quot;openjpa.DataCache property to &quot;dynacache&quot; .
  </MsgText>
  <Explanation>
    This message is for informational purposes only.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="DYNA1088I" severity="I" prefix="yes">
  <MsgText pgmKey="incompatible-configuration3" varFormat="Java">
    incompatible-configuration3=DYNA1088I: Since the openjpa.Datacache property  is set to &quot;dynacache&quot; the Dynacache OpenJPA L2 Cache Provider will FORCE set openjpa.RemoteCommitProvider property to &quot;none&quot;.
  </MsgText>
  <Explanation>
    This message is for informational purposes only.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="DYNA1087I" severity="I" prefix="yes">
  <MsgText pgmKey="incompatible-configuration2" varFormat="Java">
    incompatible-configuration2=DYNA1087I: Since the openjpa.DataCacheManager property is set to &quot;dynacache&quot; the Dynacache OpenJPA L2  Cache Provider will FORCE set the openjpa.RemoteCommitProvider property to &quot;none&quot;.
  </MsgText>
  <Explanation>
    This message is for informational purposes only.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="DYNA1086I" severity="I" prefix="yes">
  <MsgText pgmKey="incompatible-configuration1" varFormat="Java">
    incompatible-configuration1=DYNA1086I: Since the openjpa.DataCacheManager property is set to &quot;dynacache&quot;  the Dynacache OpenJPA L2 Cache Provider will FORCE set the openjpa.DataCache property to &quot;dynacache&quot;.
  </MsgText>
  <Explanation>
    This message is for informational purposes only.
  </Explanation>
  <UserResponse>
    No action is required.
  </UserResponse>
</Message>
<Message ID="DYNA1014E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1014E" varFormat="Java">
    DYNA1014E=DYNA1014E: Method {0}: Entry should have been in our push/pull table, but servant token is null. entryKey = {1}
  </MsgText>
  <Explanation>
    The specified method could not retrieve the cacheEntry from the push/pull table because the servant owner token is null.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0055E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0055E" varFormat="Java">
    DYNA0055E=DYNA0055E: Offload to disk is disabled for cache name &quot;{0}&quot; because the location &quot;{1}&quot; or &quot;{2}&quot; cannot be created.
  </MsgText>
  <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.
  </Explanation>
  <UserResponse>
    Make sure the disk offload location has sufficient access privileges.
  </UserResponse>
</Message>
<Message ID="DYNA0017I" severity="I" prefix="yes">
  <MsgText pgmKey="dynacache.joingroup" varFormat="Java">
    dynacache.joingroup=DYNA0017I: Joined group {0}
  </MsgText>
  <Explanation>
    This cache unit successfully joined a group of cooperating caches.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1053E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1053E" varFormat="Java">
    DYNA1053E=DYNA1053E: Exception occurred while trying to invoke MBean command &quot;{0}&quot;. Exception: {1}
  </MsgText>
  <Explanation>
    Exception occurred while trying to invoke MBean command.
  </Explanation>
  <UserResponse>
    See the explanation of the exception described in the error message.
  </UserResponse>
</Message>
<Message ID="DYNA0054W" severity="W" prefix="yes">
  <MsgText pgmKey="DYNA0054W" varFormat="Java">
    DYNA0054W=DYNA0054W: Offload to disk is enabled for cache name &quot;{0}&quot;. The location &quot;{1}&quot; cannot be created. The default alternate location &quot;{2}&quot; is used instead.
  </MsgText>
  <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.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0011E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.fileNotFound" varFormat="Java">
    dynacache.fileNotFound=DYNA0011E: Servlet cache file {0} not found; caching is disabled
  </MsgText>
  <Explanation>
    The specified caching properties were not specified for this application server. Caching is disabled.
  </Explanation>
  <UserResponse>
    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.
  </UserResponse>
</Message>
<Message ID="DYNA1049E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1049E" varFormat="Java">
    DYNA1049E=DYNA1049E: DynaCache MBean was not found in the node &quot;{0}&quot; on which the server &quot;{1}&quot; resides.
  </MsgText>
  <Explanation>
    DynaCache MBean was not found in the node on which the server resides.
  </Explanation>
  <UserResponse>
    Check the query expression for the MBean. Ensure that the node and the server names provided exist.
  </UserResponse>
</Message>
<Message ID="DYNA1013E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1013E" varFormat="Java">
    DYNA1013E=DYNA1013E: Method {0}: entryKeyBytes is null: entryKey = {1}  entryKeyBytes = {2}
  </MsgText>
  <Explanation>
    The specified method cannot call the proxy because entryKeyBytes is null.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1092E" severity="E" prefix="yes">
  <MsgText pgmKey="no-jpa-cache-exists-with-this-name" varFormat="Java">
    no-jpa-cache-exists-with-this-name=DYNA1092E: No DataCache with name &quot;{0}&quot; exists.
  </MsgText>
  <Explanation>
    Please confirm that the L2 DataCache was created successfully.
  </Explanation>
  <UserResponse>
    Please confirm that the L2 Data Cache is correct.
  </UserResponse>
</Message>
<Message ID="DYNA1009E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1009E" varFormat="Java">
    DYNA1009E=DYNA1009E: Method {0}: token is null.
  </MsgText>
  <Explanation>
    The specified method was passed a null servant token.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1052E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1052E" varFormat="Java">
    DYNA1052E=DYNA1052E: The input name &quot;{0}&quot; is not a valid cache statistic name.
  </MsgText>
  <Explanation>
    The input cache statistic name is not valid.
  </Explanation>
  <UserResponse>
    Ensure that the cache statistics name is valid.
  </UserResponse>
</Message>
<Message ID="DYNA0020E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.notSerializable" varFormat="Java">
    dynacache.notSerializable=DYNA0020E: Unable to cache {0}, request attributes can not be serialized.
  </MsgText>
  <Explanation>
    Servlet output was marked to be replicated between caches, which requires that all request attributes are able to be serialized.
  </Explanation>
  <UserResponse>
    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.
  </UserResponse>
</Message>
<Message ID="DYNA1048E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1048E" varFormat="Java">
    DYNA1048E=DYNA1048E: MBean command &quot;{0}&quot; can only run under Deployment Manager.
  </MsgText>
  <Explanation>
    MBean command &quot;CompareCaches&quot; can only run under Deployment Manager.
  </Explanation>
  <UserResponse>
    Run the CompareCaches command from the Deployment Manager Dynacache MBean.
  </UserResponse>
</Message>
<Message ID="DYNA0012I" severity="I" prefix="yes">
  <MsgText pgmKey="dynacache.cachingEnabled" varFormat="Java">
    dynacache.cachingEnabled=DYNA0012I: Dynamic servlet caching is enabled
  </MsgText>
  <Explanation>
    Dynamic servlet caching is enabled.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1012E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1012E" varFormat="Java">
    DYNA1012E=DYNA1012E: Method {0}: eventBytes is null: event = {1}  eventBytes = {2}
  </MsgText>
  <Explanation>
    The specified method cannot call the proxy because eventBytes is null.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1008E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1008E" varFormat="Java">
    DYNA1008E=DYNA1008E: Method {0}: proxy is null.
  </MsgText>
  <Explanation>
    The specified method was unable to obtain a servant proxy for DRS.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0053I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA0053I" varFormat="Java">
    DYNA0053I=DYNA0053I: Offload to disk is enabled for cache named &quot;{0}&quot; in directory &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    The disk offload feature is enabled for the specified cache name. The disk cache is stored in the specified directory.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA0023E" severity="E" prefix="yes">
  <MsgText pgmKey="dynacache.nullServletMapping" varFormat="Java">
    dynacache.nullServletMapping=DYNA0023E: Error building cache policy {0}.  There are no servlet mappings defined for servlet {1}
  </MsgText>
  <Explanation>
    Could not find a servlet mapping for the cache servlet or JSP file.
  </Explanation>
  <UserResponse>
    Correct the configuration error using the application assembly tool.
  </UserResponse>
</Message>
<Message ID="DYNA1091E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1091E" varFormat="Java">
    DYNA1091E=DYNA1091E: Configuration for cache instance &quot;{0}&quot;, was not recognized due to exception &quot;{0}&quot;.
  </MsgText>
  <Explanation>
    The Dynamic Cache configuration for cache instance is invalid because of the thrown exception.
  </Explanation>
  <UserResponse>
    Please correct and address at the cause of the exception so that the cache configuration can be successfully added to the Dynamic Cache runtime.
  </UserResponse>
</Message>
<Message ID="DYNA0049E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0049E" varFormat="Java">
    DYNA0049E=DYNA0049E: Unrecognized component type {0}.
  </MsgText>
  <Explanation>
    The specified component type was present in the cache configuration file, but is not recognized by the cache.
  </Explanation>
  <UserResponse>
    Remove the unrecognized component type from the cache configuration file.
  </UserResponse>
</Message>
<Message ID="DYNA1051E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1051E" varFormat="Java">
    DYNA1051E=DYNA1051E: The MBean command &quot;{0}&quot; cannot be performed because the disk offload feature is not enabled for named cache instance &quot;{1}&quot;.
  </MsgText>
  <Explanation>
    The MBean command cannot be envoked because the disk offload feature is not enabled for the named cache instance.
  </Explanation>
  <UserResponse>
    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.
  </UserResponse>
</Message>
<Message ID="DYNA1047E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1047E" varFormat="Java">
    DYNA1047E=DYNA1047E: Internal error: Failure to create AdminService object. Exception: {0}
  </MsgText>
  <Explanation>
    Internal error: Failure to create AdminService object.
  </Explanation>
  <UserResponse>
    Contact IBM service for debugging this problem.
  </UserResponse>
</Message>
<Message ID="DYNA1011E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA1011E" varFormat="Java">
    DYNA1011E=DYNA1011E: Method {0}: tokenBytes is null: token = {1}  tokenBytes = {2}
  </MsgText>
  <Explanation>
    The specified method cannot call the proxy because tokenBytes is null.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1007I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1007I" varFormat="Java">
    DYNA1007I=DYNA1007I:  {0} service has initialized successfully.
  </MsgText>
  <Explanation>
    The z/OS Controller Service for the dynamic cache service has initialized successfully.
  </Explanation>
  <UserResponse>
    None.
  </UserResponse>
</Message>
<Message ID="DYNA1090I" severity="I" prefix="yes">
  <MsgText pgmKey="DYNA1090I" varFormat="Java">
    DYNA1090I=DYNA1090I: Dynamic Cache service is disabled.
  </MsgText>
  <Explanation>
    The Dynamic  Cache, Object cache and Servlet caching services have been disabled through the administrative console or scripting.
  </Explanation>
  <UserResponse>
    Enable the Dynamic Cache service by setting the &quot;enable&quot; attribute of the server scoped &quot;DynamicCache&quot; AdminConfig object or through the administrative console panel Application servers &gt; &lt;server_name&gt; &gt; Dynamic cache service
  </UserResponse>
</Message>
<Message ID="DYNA0052E" severity="E" prefix="yes">
  <MsgText pgmKey="DYNA0052E" varFormat="Java">
    DYNA0052E=DYNA0052E: The cached object can not be replicated or saved to disk.  CacheID={0}   ClassName={1}   Type={2}    Exception={3}
  </MsgText>
  <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.
  </Explanation>
  <UserResponse>
    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.
  </UserResponse>
</Message>
<!-- END MESSAGES -->
</TMSSource>
