WebSphere Process Server messages     Operating Systems: All supported

DYNA

DYNA0001E: The priority value was not a valid number for entry {0}. Use an integer instead of {1}.
Problem The user entered a non-integer or non-positive integer for the priority.
User response 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}.
Problem The user entered a non-integer for the timeout.
User response Change the timeout value to a numeral integer.
DYNA0003E: Not caching {0} due to misconfiguration.
Problem The servlet specified was incorrectly configured for an unknown reason.
User response Check that legal, non-contradictory values have been given, and that all required fields are specified.
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.
Problem A servlet was configured with trivial configuration information. This is legal, though unlikely correct, except for the simplest cases.
User response Verify that the servlet to be cached requires only the invocation URI to determine uniqueness.
DYNA0005E: Duplicate ExternalCacheGroup entry for address {0}.
Problem A duplicate ExternalCacheGroup was entered in the configuration.
User response Remove the duplicate group.
DYNA0006E: ExternalCacheGroup {0} was not found.
Problem The external cache group to which this servlet output should be forwarded, was not registered in the global cache configuration.
User response Check the spelling of this external cache group. If correct, define this group in the global cache properties.
DYNA0007E: Error initializing external cache adapter: {0}
Problem The specified error was thrown during external cache adapter initialization.
User response Identify the cause of the error from the error specific information provided in the message
DYNA0008E: CacheUnit no longer exists.
Problem A message was either sent or received from a cache unit that is no longer registered with this cache unit with a cache replication group.
User response Verify that the specified cache unit should be active; if so, restart the server.
DYNA0009E: No element named {0} in document {1}.
Problem When parsing the document specified, an expected XML element was not found.
User response Check the XML file format against the documentation, looking for a misconfiguration.
DYNA0010E: No element named {0} in {1}.
Problem When parsing the configuration XML files, an expected XML element was not found.
User response Check the XML file format against the documentation, looking for a misconfiguration.
DYNA0011E: Servlet cache file {0} not found; caching is disabled
Problem The specified caching properties were not specified for this application server. Caching is disabled.
User response Build a cache configuration XML file with the specified name. See documentation for instructions on building this file.
DYNA0012I: Dynamic servlet caching is enabled
Problem Dynamic servlet caching is enabled.
User response None.
DYNA0013I: Dynamic servlet caching is disabled
Problem Dynamic servlet caching is disabled.
User response None.
DYNA0014I: {0} is a cacheable URI
Problem A servlet or JSP was initialized that has a valid cache policy configured.
User response None.
DYNA0015I: Dynamic Servlet Caching encountered an error: {0}
Problem General error message.
User response Debug the provided error.
DYNA0016I: Dumped dynamic servlet caching statistics to: {0}
Problem Cache statistics were written to the specified file.
User response None.
DYNA0017I: Joined group {0}
Problem This cache unit successfully joined a group of cooperating caches.
User response None.
DYNA0018E: Error loading ID Generator {0}
Problem Error loading ID Generator.
User response Debug the problem using the provided error message.
DYNA0019E: Error loading MetaData Generator {0}
Problem Error loading MetaData Generator.
User response Debug the problem using the provided error message.
DYNA0020E: Unable to cache {0}, request attributes can not be serialized.
Problem Servlet output was marked to be replicated between caches, which requires that all request attributes are able to be serialized.
User response Modify the cache policy for this servlet so that its output is not replicated, or modify the application so that all request attributes can be serialized.
DYNA0021E: Unable to initialize cache unit {0}: {1}
Problem Unanticipated error initializing the cache.
User response Debug the problem using the provided error message.
DYNA0022E: Error processing dynamic cache configuration: {0}
Problem Unanticipated error processing cache configuration.
User response Debug the problem using the provided error message.
DYNA0023E: Error building cache policy {0}. There are no servlet mappings defined for servlet {1}
Problem Could not find a servlet mapping for the cache servlet or JSP.
User response 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}.
Problem Duplicate exclude variables were present.
User response Remove the duplicate or incorrectly defined excludes 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.
Problem An entry was marked as externally cacheable, but also contained additional id generation rules.
User response Remove the additional rules.
DYNA0026E: Error reading element {0}. While processing value {1}, received exception: {2}.
Problem An error occurred while reading the cache configuration file.
User response Correct the error using the provided information.
DYNA0027E: Unrecognized replication policy: {0}.
Problem An unrecognized replication policy was specified.
User response 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.
Problem A cache policy specified both a component and idgenerator for the same cache id rule.
User response You must either use either component tags or an idgenerator but not both simultaneously.
DYNA0029E: Illegal use of idgenerator {0} when component {1} is already defined.
Problem A cache policy specified both a component and idgenerator for the same cache id rule.
User response You must either use either component tags or an idgenerator but not both simultaneously.
DYNA0030E: {0} element is missing required attribute "{1}".
Problem A required attribute was missing in the cache configuration.
User response 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.
Problem The configuration file specified multiple method or field tags for the same component.
User response Eliminate the duplicate method and/or field elements from the component in the configuration file.
DYNA0032E: Element or attribute "{0}" must be set to either the value "true" or "false". Value present: {0}.
Problem The specified element must have a value of either true or false, but another value was specified.
User response Correct the element to have the value "true" or "false".
DYNA0033E: Unable to introspect method {0} from class {1}. Exception: {2}
Problem An error occurred while trying to locate the specified method as specified in the cache configuration file.
User response Verify that the method specified in the cache configuration file exists in the object being invoked and the method is public.
DYNA0034E: Exception invoking method {0} on class {1}. Exception: {2}
Problem An error occurred while invoking the specified method to generate a cache id.
User response Debug the problem using the provided error message.
DYNA0035E: Unable to introspect field {0} from class {1}. Exception: {2}
Problem An error occurred while trying to locate the specified field as specified in the cache configuration file.
User response Verify that the field specified in the cache configuration file exists in the object being invoked and the field is public.
DYNA0036E: Exception retrieving field {0} from class {1}. Exception: {2}
Problem An error occurred while retrieving the specified field to generate a cache id.
User response Debug the problem using the provided error message.
DYNA0037E: Unrecognized element {0} while processing element {1}.
Problem An unrecognized element was encountered while parsing the cache configuration file.
User response Correct the document to match the cachespec.dtd.
DYNA0038E: Unrecognized component type {0} for command {1}.
Problem The specified component type is not valid for command caching.
User response Valid component types for commands are "method" and "field".
DYNA0039E: Commands do not support custom metadata generating classes. You must override the prepareMetaData() method.
Problem The cache configuration file specified a custom metadata generator for a command, but this is not supported.
User response Read the product documentation on implementing the CacheableCommand.prepareMetaData method.
DYNA0040E: Illegal component type {0} servicing {1}.
Problem An unsupported component type was encountered while processing the specified object.
User response Correct the cache configuration policy to contain only valid component types for the specified object.
DYNA0041E: Invalid component type {0} for edgeable fragment {1}.
Problem A servlet or JSP was marked Edgeable, but the cache policy contains component rules which are not valid on an edge server.
User response Correct the cache policy to eliminate the rules that are not executable at the Edge Server, or mark the servlet/JSP as not edgeable.
DYNA0042E: Invalid component type {0} for servlet/jsp fragment {1}.
Problem An unsupported component type was encounted while processing the specified servlet or JSP.
User response Correct the cache configuration policy to contain only valid component types for the specified object.
DYNA0043E: Configuration file {0} contained errors and will not be used.
Problem The specified configuration file contained critical errors and cannot be utilized.
User response Correct the specified errors in the configuration file.
DYNA0044E: XML parsing warning: {0}, while parsing file {1} at line {2}, column {3}.
Problem An XML parsing warning occurred while processing a cache configuration file.
User response Correct the problem specified in the message.
DYNA0045E: XML parsing error: {0}, while parsing file {1} at line {2}, column {3}.
Problem An XML parsing warning occurred while processing a cache configuration file.
User response Correct the problem specified in the message.
DYNA0046E: I/O exception {0} occurred while processing configuration file {1}.
Problem An error occurred while reading the cache configuration file.
User response Correct the problem specified in the message.
DYNA0047I: Successfully loaded cache-entries from cache configuration file {0}.
Problem This message indicates that a cache configuration file was successfully processed for cache-entries from the specified location.
User response None.
DYNA0048I: WebSphere Dynamic Cache initialized successfully.
Problem This message indicates that the WebSphere Dynamic Cache was successfully initialized.
User response None.
DYNA0049E: Unrecognized component type {0}.
Problem The specified component type was present in the cache configuration file, but is not recognized by the cache.
User response Remove the unrecognized component type from the cache configuration file.
DYNA0050E: Unrecognized value {0} for element {1}.
Problem The specified element in the cache configuration file contained an unrecognized value.
User response Consult the WebSphere documentation for valid values for the specified element. Correct the problem.
DYNA0051E: Could not cache a CacheableCommand because WebSphere Dynamic Caching is disabled.
Problem An attempt was made to use a CacheableCommand, but WebSphere Dynamic Caching is disabled.
User response Enable the WebSphere Dynamic Cache so that the command can be cached.
DYNA0052E: The cached object can not be replicated or saved to disk. CacheID={0} ClassName={1} Exception={2}
Problem The object was marked to be replicated between caches or saved to disk which requires the object and all referenced objects within the object be serializable. CacheID is the id of the cache entry that can not be serialized. ClassName is the class name of the cached object that can not be serialized. Exception is the exception received during the serialization attempt.
User response Modify the cache policy for this object so that it is not replicated or saved to disk or modify the application so the object and all referenced objects are serializable.
DYNA0053I: Offload to disk is enabled for cache named "{0}" in directory "{1}".
Problem This message indicates that offload to disk is enabled for the specified cache name. The disk cache is stored in the specified directory.
User response None.
DYNA0054W: Offload to disk is enabled for cache name "{0}". The location "{1}" cannot be created. The default alternate location "{2}" is used instead.
Problem This message indicates that offload to disk is enabled for the specified cache name. The disk cache is stored in the alternate location because specified directory cannot be created.
User response None.
DYNA0055E: Offload to disk is disabled for cache name "{0}" because the location "{1}" or "{2}" cannot be created.
Problem This message indicates that offload to disk is disabled for the specified cache name because disk offload location and default alternate location cannot be created.
User response Make sure the disk offload location has sufficient access privileges.
DYNA0056W: Disk cache files have been reinitialized because of corrupted data.
Problem This message indicates that the disk cache files have been reinitialized because of corrupted data. This may have been caused by an unexpected JVM termination or a disk exception occurred before the server was restarted. All old disk cache contents are lost.
User response None.
DYNA0057I: The disk cache cleanup started for the cache name "{0}". The statistics are: {1}
Problem This message indicates that the disk cache cleanup has started to remove expired cache entries.
User response No user action is required.
DYNA0058I: The disk cache cleanup finished for cache name "{0}". The statistics are: {1}
Problem This message indicates that the disk cache cleanup is finished.
User response No user action is required.
DYNA0059I: The disk cache configuration for cache name "{0}". The configuration is: {1}
Problem This message shows the disk cache configuration.
User response No user action is required.
DYNA0060I: Flush to disk on stop is enabled for cache name "{0}".
Problem This message indicates that flush to disk on stop is enabled for the specified cache name
User response No user action is required.
DYNA0061I: Flush to disk on stop is disabled for cache name "{0}".
Problem This message indicates that flush to disk on stop is disabled for the specified cache name
User response No user action is required.
DYNA0062I: Successfully loaded cache-instances from configuration file {0}.
Problem This message indicates that a cache configuration file was successfully processed for cache-instances from the specified location.
User response 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.
Problem The cached object will not be offloaded to disk because it is over the disk cache size in GB limit.
User response Modify the custom property "diskCacheSizeInGB" to a larger value so that it can store more caches in the disk.
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.
Problem The cached object will not be offloaded to disk because it is over the disk cache size in MB limit.
User response Modify the custom property "diskCacheEntrySizeInMB" to a larger value so that it can store more caches in the disk.
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.
Problem The cached object will not be offloaded to disk because it is over the disk cache size limit.
User response Modify the custom property "diskCacheSize" to a larger value so that it can store more caches in the disk.
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.
Problem The disk files on the system are in an old format and the limiting disk cache size in GB feature uses a new disk format. Before enabling this feature delete all disk cache files on the system.
User response Delete all disk cache files and then restart the server.
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.
Problem The disk files on the system are in an old format and the disk cache garbage collection feature uses a new disk format. Before enabling this feature delete all disk cache files on the system.
User response Delete all disk cache files and then restart the server.
DYNA0068W: Invalid disk threshold set for cache name "{0}". Using default values of 80% and 70% for high and low threshold limits respectively.
Problem The disk cache threshold limit has either been set < 0 or high threshold is lower than low threshold limit.
User response The disk cache threshold should be greater than 0 and high threshold limit should be greater than low threshold limit.
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}".
Problem An invalid value for custom property is found. Correct the value using the range-specified low and high values in the warning message.
User response Correct the value using the range-specified low and high values in the warning message.
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.
Problem It is required to set custom properties "diskCacheSize" or "diskCacheSizeInGB" in order to use the disk cache garbage collector feature.
User response Set the custom properties "diskCacheSize" or "diskCacheSizeInGB" and restart the server.
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}".
Problem The disk cache files cannot shrink.
User response To set custom property "diskCacheSizeInGB" to a smaller value, delete all disk cache files and restart the server.
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}".
Problem This message indicates that offload to disk is disabled for the specified cache name because a disk exception has occurred.
User response The disk cache files for this cache instance will be deleted when the server is restarted.
DYNA0073I: Flush to disk on stop for cache name "{0}" has completed. The statistics are: {1}
Problem This message indicates that flush to disk on stop operation has completed with the statistics.
User response No user action is required.
DYNA1001I: WebSphere Dynamic Cache instance named {0} initialized successfully.
Problem This message indicates the named WebSphere Dynamic Cache instance was successfully initialized.
User response None.
DYNA1002E: WebSphere Dynamic Cache instances can not be initialized because of error {0}.
Problem This message indicates the WebSphere Dynamic Cache instances can not be initialized. No caches instances are avaliable.
User response Debug the problem using error message {0}. The WebSphere logs will contain additional information.
DYNA1003E: WebSphere Dynamic Cache instance named {0} can not be initialized because of error {1}.
Problem This message indicates the named WebSphere Dynamic Cache instance can not be initialized. The named instance is not avaliable.
User response Debug the problem using error message {1}. The WebSphere logs will contain additional information.
DYNA1004E: WebSphere Dynamic Cache instance named {0} can not be initialized because it is not configured.
Problem This message indicates the named WebSphere Dynamic Cache instance can not be initialized. Dynamic caching is disabled for the named instance.
User response Use the WebSphere Administrative Console to configure a cache instance resource named {0}.
DYNA1005E: WebSphere Dynamic Cache instance named {0} can not be accessed because it is the wrong type.
Problem This message indicates the named WebSphere Dynamic Cache instance can not be used. Dynamic caching is disabled for the named instance.
User response Use the WebSphere Administrative Console to configure a cache instance resource named {0} using the correct type.
DYNA1006E: Method {0} caught exception: {1}
Problem An exception was caught in the specified method.
User response None.
DYNA1007I: {0} service has initialized successfully.
Problem The z/OS Controller Service for Dynacache has initialized successfully.
User response None.
DYNA1008E: Method {0}: proxy is null.
Problem The specified method was unable to obtain a servant proxy for DRS.
User response None.
DYNA1009E: Method {0}: token is null.
Problem The specified method was passed a null servant token.
User response None.
DYNA1010E: Method {0}: Parameter error: entryKey is null.
Problem The specified method was passed a null entryKey parameter.
User response None.
DYNA1011E: Method {0}: tokenBytes is null: token = {1} tokenBytes = {2}
Problem The specified method cannot call the proxy because tokenBytes is null.
User response None.
DYNA1012E: Method {0}: eventBytes is null: event = {1} eventBytes = {2}
Problem The specified method cannot call the proxy because eventBytes is null.
User response None.
DYNA1013E: Method {0}: entryKeyBytes is null: entryKey = {1} entryKeyBytes = {2}
Problem The specified method cannot call the proxy because entryKeyBytes is null.
User response None.
DYNA1014E: Method {0}: Entry should have been in our push/pull table, but servant token is null. entryKey = {1}
Problem The specified method could not retrieve the cacheEntry from the push/pull table because the servant owner token is null.
User response None.
DYNA1015E: Method {0}: propKeyBytes is null: propKey = {1} propKeyBytes = {2}
Problem The specified method cannot call the proxy because propKeyBytes is null.
User response None.
DYNA1016E: Method {0}: dbmBytes is null: dbm = {1} dbmBytes = {2}
Problem The specified method cannot call the proxy because the DRSBootstrapMsg converted to bytes is null.
User response None.
DYNA1017E: Method {0}: Parameter error: dbm is null.
Problem The specified method was passed a null dbm object.
User response None.
DYNA1018E: Method {0}: Value tmp returned by proxy.handleBootstrapRequest is null: tmp = {1}, token = {2}
Problem For the specified method the returned value from proxy.handleBootstrapRequest is null.
User response None.
DYNA1019E: Method {0}: Parameter error: propKey is null.
Problem The specified method was passed a null propKey parameter.
User response None.
DYNA1020E: Method {0}: Parameter error: value is null.
Problem The specified method was passed a null for the value parameter.
User response None.
DYNA1021E: Method {0}: Cannot convert the value parameter to bytes.
Problem The specified method is unable to convert the value parameter to bytes.
User response None.
DYNA1022E: Method {0}: Parameter error: DRSJvmId routing information is null.
Problem The specified method was passed a null for the DRSJvmId routing parameter.
User response None.
DYNA1023E: Method {0}: Parameter error: entryKeyList is null.
Problem The specified method was passed a null for the entryKeyList.
User response None.
DYNA1024E: Method {0}: Cannot convert the entryKeyList to bytes - entryKeyList = {1} entryKeyListBytes = {2}
Problem The specified method is unable to convert the entryKeyList parameter to a byte array.
User response None.
DYNA1025E: Method {0}: Cannot convert the DRSJvmId to bytes - jvmId = {1} jvmIdBytes = {2}
Problem The specified method is unable to convert the DRSJvmID parameter to a byte array.
User response None.
DYNA1026I: DynacacheDRSController DRS Instance {0} received event REPLICATION_UP.
Problem The specified DynacacheDRSController DRS Instance received event REPLICATION_UP.
User response None.
DYNA1027I: DynacacheDRSController DRS Instance {0} received event REPLICATION_DOWN.
Problem The specified DynacacheDRSController DRS Instance received event REPLICATION_DOWN.
User response None.
DYNA1028I: DynacacheDRSController DRS Instance {0} received event IS_CONGESTED.
Problem The specified DynacacheDRSController DRS Instance received event IS_CONGESTED.
User response None.
DYNA1029I: DynacacheDRSController DRS Instance {0} received event NOT_CONGESTED.
Problem The specified DynacacheDRSController DRS Instance received event NOT_CONGESTED.
User response None.
DYNA1030E: Invalid range values, low: {0} and high: {1} attributes must be integers
Problem A required attribute was missing in the cache configuration.
User response Add the required attribute to your cache configuration file.
DYNA1031E: Invalid range, low atribute: {0} is greater than high attribute: {1}.
Problem The low and high attribute values specified for the range are not valid.
User response Correct the the low and high attributes values such that the low value is less than the high value.
DYNA1032E: Property with name "primary-storage" must be set to either the value "memory" or "disk". Value present: {0}.
Problem The specified element must have a value of either memory or disk, but another value was specified.
User response Correct the element to have the value "memory" or "disk".
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}.
Problem The setting of custom property "disableDependencyId" does not match the current state of disk files.
User response To set custom property "disableDependencyId" to your desired settings, delete all disk cache files and restart the server.
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}.
Problem The setting of custom property "disableTemplatesSupport" does not match the current state of disk files.
User response To set custom property "disableTemplatesSupport" to your desired settings, delete all disk cache files and restart the server.
Reference topic    

Terms of Use | Feedback

Last updated: Jun 13, 2009 1:00:35 PM CDT
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.messages.doc/com.ibm.ws.cache.resources.dynacache.html

© Copyright IBM Corporation 2006, 2009. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)