Symptom:
I have entries in the SA Manager log (soimgr.log) and the UI Server log (soiuis.log) with warnings similar to the following examples:
2013-10-15 11:23:32,547 WARN [WrapperStartStopAppMain] config.ConfigurationFactory.parseConfiguration(133) - 2013/10/15 11:23:32:538 EDT [WARN] ConfigurationFactory - No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/E:/CA/SOI/wso2registry/repository/components/plugins/ehcache-1.5.0.wso2v1.jar!/ehcache-failsafe.xml
2013-10-15 11:23:33,139 WARN [WrapperStartStopAppMain] config.ConfigurationFactory.parseConfiguration(133) - 2013/10/15 11:23:33:138 EDT [WARN] ConfigurationFactory - No configuration found. Configuring ehcache from ehcache-failsafe.xml found in the classpath: jar:file:/E:/CA/SOI/wso2registry/repository/components/plugins/ehcache-1.5.0.wso2v1.jar!/ehcache-failsafe.xml
2013-10-15 11:23:33,198 WARN [WrapperStartStopAppMain] ehcache.CacheManager.detectAndFixDiskStorePathConflict(322) - 2013/10/15 11:23:33:197 EDT [WARN] CacheManager - Creating a new instance of CacheManager using the diskStorePath "../../samui/temp" which is already used by an existing CacheManager.
The source of the configuration was classpath.
The diskStore path for this CacheManager will be set to ../../samui/temp\ehcache_auto_created_1381850613197.
To avoid this warning consider using the CacheManager factory methods to create a singleton CacheManager or specifying a separate ehcache configuration (ehcache.xml) for each CacheManager instance.
Solution:
These warning messages generates when you restart the SA Manager and UI Server services. Ignore the warnings.
|
Copyright © 2013 CA.
All rights reserved.
|
|