project_key: JBEPP
Link: Added: This issue is related to GTNPORTAL-1545
Release Notes Docs Status: Added: Not Required
Release Notes Docs Status: Removed: Not Required Added: Documented as Resolved Issue Release Notes Text: Added: "Cannot find the configuration for the component org.exoplatform.portal.webui.container.UIContainerList, configId null" could be logged under heavy load.
Release Notes Text: Removed: "Cannot find the configuration for the component org.exoplatform.portal.webui.container.UIContainerList, configId null" could be logged under heavy load. Added: The use of HashMap in the ConfigurationManager class for multithreaded environments in previous versions of EPP caused the following message to appear in logs while using the product under heavy load: "java.lang.Exception: Cannot find the configuration for the component org.exoplatform.portal.webui.container.UIContainerList, configId null". In the latest release, HashMap has been replaced with ConcurrentHashMap, which accepts default values for initial capacity, load factor and concurrencyLevel and resolves the exception.
Release Notes Text: Removed: The use of HashMap in the ConfigurationManager class for multithreaded environments in previous versions of EPP caused the following message to appear in logs while using the product under heavy load: "java.lang.Exception: Cannot find the configuration for the component org.exoplatform.portal.webui.container.UIContainerList, configId null". In the latest release, HashMap has been replaced with ConcurrentHashMap, which accepts default values for initial capacity, load factor and concurrencyLevel and resolves the exception. Added: Previous versions of EPP used HashMap in the ConfigurationManager class for multithreaded environments. This caused the following message to appear in logs while using the product under heavy load: "java.lang.Exception: Cannot find the configuration for the component org.exoplatform.portal.webui.container.UIContainerList, configId null". In the latest release, HashMap has been replaced with ConcurrentHashMap, which accepts default values for initial capacity, load factor and concurrencyLevel and resolves the exception.
Link: Added: This issue related JBEPP-657
Rolledback in favor of the duplicate issue fix