|
BEA-130000
|
Warning: Insertion of arg0 into XML entity cache rejected. Entity size, arg1, exceeded cache size, arg2.
|
Description
| XML Entities to be cached cannot be larger than the size of the cache itself. The cache has rejected the entity. |
|
Cause
| The cache may be too small or a specific item might be legitimately very large. The worst case is that this indicates a denial of service attack. |
|
Action
| No action required. However, performance will be best if items are cached. |
|
|
BEA-130001
|
Warning: Entity cache appears to be broken. This impacts the performance of XML parsing.
|
Description
| Attempts to insert or retrieve items from the XML entity cache are failing for unknown reasons. This does not prevent XML parsing, but parse performance will be impacted. Also, the cache provides a fallback in the case of a network failure. If the cache is not operational, this fullback is not in effect. |
|
Cause
| Unknown |
|
Action
| No action is required. However, performance will increase if items are cached. Also the cache provides a fallback in the case of a network failure. While the cache is not operating, this fullback is not in effect. |
|
|
BEA-130002
|
Warning: The entity that was just put in the cache cannot be retrieved: " arg0. Timeout may be too short.
|
Description
| A check is made just after an entity is added to the cache to ensure that that entity can be retrieved. The test failed for the current entity. |
|
Cause
| Usually this indicates that the entity timeout was set to a very small value. Otherwise there is some unknown problem with the cache module itself. |
|
Action
| No action is required, but XML parse performance will be impacted. Also there is no cached copy to act as a backup in the event of a network failure. |
|
|
BEA-130003
|
Error: Could not instantiate factory class specified in the server console. message
|
Description
| The factory class specified in the console could not be instantiated. The factory can be of type: SAXParserFactory, DocumentBuilderFactory, or TransformerFactory. Proceeding with default WebLogic factory. |
|
Cause
| Class name of the factory is not correct or it is not in the CLASSPATH. |
|
Action
| Check your CLASSPATH or verify your console entry. |
|
|
BEA-130006
|
Warning: XML cache warning for registry registry: Entry rejection due to entry being larger than the cache memory size. Entry: entry Entry memory size: memSize
|
Description
| Entry exceeds cache memory size. |
|
Cause
| The entry is larger than the cache. |
|
Action
| No action required unless you want the item to be cached next time. If so, increase the cache memory size. |
|
|
BEA-130007
|
Info: XML cache event: memory purge of count entries of combined size combinedSize. Current memory usage is memUsage bytes.
|
|
BEA-130008
|
Info: XML cache event: disk purge of count entries of combined size combinedSize. Current disk usage is diskUsage bytes.
|
|
BEA-130009
|
Warning: XML cache warning for registry registry: Entry persist attempt rejected due to entry being larger than the cache disk size. Status changed to transient. Entry: entry Entry disk size: diskSize
|
Description
| This entry exceeds established limits on the cache disk space. |
|
Cause
| The size of the entry on the disk exceeds the allocated disk space. |
|
Action
| No action is required. If you want the entry to be persisted next time, increase the disk size of the cache. |
|
|
BEA-130010
|
Info: XML cache event for registry registry: Entry added. Entry: entry Entry memory size: memSize StorageType: storageType Current memory usage (bytes): memUsage
|
|
BEA-130011
|
Info: XML cache event for registry registry: Entry deleted. Entry: entry Entry memory size: memSize Entry disk size: diskSize Current memory usage (bytes): memUsage Current disk usage (bytes): diskUsage
|
|
BEA-130012
|
Info: XML cache event for registry registry: Entry persisted. Entry: entry Entry disk size: diskSize Current disk usage (bytes): diskUsage
|
|
BEA-130013
|
Info: XML cache event for registry registry: Entry loaded. Entry: entry Entry memory size: memSize Current memory usage (bytes): memUsage
|
|
BEA-130014
|
Info: XML cache event: Statistics checkpointed.
|
|
BEA-130015
|
Info: XML cache event: cache created. Current memory usage (bytes): memUsage Current disk usage (bytes): diskUsage
|
|
BEA-130016
|
Info: XML cache event: cache loaded. Current memory usage (bytes): memUsage Current disk usage (bytes): diskUsage
|
|
BEA-130017
|
Info: XML cache event: Cache closed. Current disk usage (bytes): diskUsage
|
|
BEA-130018
|
Error: XML cache error: Cache file path is corrupted. Creating new cache from scratch.
|
Description
| The system has detected that the cache file has been corrupted. |
|
Cause
| This should not occur. |
|
Action
| The server should be restarted. If you have a backup of the cache files, restore them and then restart the server. |
|
|
BEA-130019
|
Error: XML cache error for registry registry: Entry file path is corrupted. Removing from cache. Entry: entry
|
Description
| The system has detected that an entry in the cache file has been corrupted. |
|
Cause
| This should not occur. |
|
Action
| The server should be restarted. The entry will be re-cached on next access. |
|
|
BEA-130020
|
Error: XML cache error: Statistics file path is corrupted. Reinitializing. Previous statistics are lost.
|
Description
| The cache file has been corrupted. |
|
Cause
| This should not occur. |
|
Action
| The server should be restarted. |
|
|
BEA-130021
|
Error: XML cache error for registry registry: Entry file path cannot be written. Status changed to transient. Entry: entry
|
Description
| An error was encountered when attempting to save a cache entry. |
|
Cause
| This is often a file protection issue. |
|
Action
| Determine why the file cannot be saved and make the appropriate adjustments. |
|
|
BEA-130022
|
Error: XML cache error: Cache file path cannot be written.
|
Description
| An error was encountered when saving the cache file. |
|
Cause
| This is often a file protection issue. |
|
Action
| Determine why the file cannot be saved and make the appropriate adjustments. |
|
|
BEA-130023
|
Error: XML cache error: Statistics file path cannot be written. No futher cache statistics for this session.
|
Description
| An error was encountered when saving the cache statistics to disk. |
|
Cause
| This is often a file protection issue. |
|
Action
| Determine why the file cannot be saved and make the appropriate adjustments. |
|
|
BEA-130024
|
Error: XML cache error for registry registry: Out of memory loading entry. Entry removed from cache. Entry: entry File: path
|
Description
| Insufficient memory to load entry from disk cache. |
|
Cause
| The entry might be unusually large or perhaps the JVM heap size is too small. |
|
Action
| Check the size of the rejected entry. If you wish to be able to handle entries of that size, increase the heap size. |
|
|
BEA-130025
|
Error: XML cache error: Out of memory loading cache. Cache not opened. File: path
|
Description
| Out of memory exception encountered when loading data from cache. |
|
Cause
| The cache file is not large, so you are close to the wall on memory usage. |
|
Action
| Increase the JVM heap size. |
|
|
BEA-130026
|
Error: XML cache error: Out of memory loading statistics. File: path
|
Description
| Out of memory exception encountered when loading statistics. |
|
Cause
| The cache file is not large, so you are close to the wall on memory usage. |
|
Action
| Increase the JVM heap size. |
|
|
BEA-130027
|
Warning: XML cache warning: The requested memory size of the XML cache, memSize, exceeds the available memory, freeMemory.
|
Description
| Insufficient memory to satisfy request. |
|
Cause
| Either the provided parameters are not in sync with usage, or something is using a lot of the available memory. |
|
Action
| Reduce the cache size or increase the JVM heap size. If you think there should be more available memory, determine what is using all the memory. |
|
|
BEA-130028
|
Warning: XML cache warning: The requested memory size of the XML cache, memSize, is a large percentage of the available memory, freeMemory.
|
Description
| This may signal a low memory condition. |
|
Cause
| Either the provided parameters are not in sync with usage, or something is using a lot of the available memory. |
|
Action
| Reduce the cache size or increase the JVM heap size. If you think that there should be more available memory, determine what is using all the memory. |
|
|
BEA-130029
|
Error: XML cache error: An unexpected error occurred in the XML cache. message
|
Description
| Unexpected exception thrown during cache processing. |
|
Cause
| Unknown cause. |
|
Action
| Refer to the associated text at the end of the message and contact support if you need help resolving the error. |
|
|
BEA-130030
|
Error: XML cache error for registry registry: The file, path, representing entry key cannot be read.
|
Description
| Check file permission. |
|
Cause
| The file is read-protected. |
|
Action
| Check the access rights and make appropriate changes. |
|
|
BEA-130031
|
Error: XML cache error: The cache file, path, cannot be read.
|
Description
| Error opening the cache file for reading. |
|
Cause
| The file is read-protected. |
|
Action
| Check the access rights and make appropriate changes. |
|
|
BEA-130032
|
Error: XML cache error: Statistics file path cannot be read.
|
Description
| An error was encountered opening the statistics file for reading. |
|
Cause
| The file is read-protected. |
|
Action
| Check the access rights and make appropriate changes. |
|
|
BEA-130033
|
Error: Parser or DocumentBuilder cannot be created to satisfy the configuration requested. message
|
Description
| Factory failed to create specified Parser or DocumentBuilder. |
|
Cause
| Misconfiguration. |
|
Action
| Verify the factory that creates the parser. Verify properties or features set on this parser. |
|
|
BEA-130034
|
Error: Failed to parse given XML document. message
|
Description
| Failed to retrieve public ID, system ID, root tag, namespace URI from the given document. |
|
Cause
| Error in the structure of the XML document. |
|
Action
| Verify XML syntax. |
|
|
BEA-130035
|
Error: Failed to open XML document. message
|
Description
| Failed or interrupted I/O operation. |
|
Cause
| File does not exist. |
|
Action
| Check file name, the file location and associated permissions. |
|
|
BEA-130036
|
Info: Initializing XMLRegistry.
|
|
BEA-130037
|
Info: Stack trace associated with message id follows: \n
|
Description
| A stack trace for a previously logged message. |
|
Cause
| An error condition was reported. |
|
Action
| No user action required. |
|
|
BEA-130038
|
Debug: msg, the property is not accepted and will be ignored: property=value.
|
Description
| Current xml parser dont recognize or support this property. |
|
Cause
| This property is specified to other xml parser, or its incorrect to all xml parsers. |
|
Action
| Dont set this property if you are sure. |
|
