Legacy Knowledge Base
Published Sep. 10, 2025

Dependency manager sync timeout after waiting 60s

Written By

Mariano Alvaro

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • The following WARN can appear during the startup:
    WARN [http-nio-8080-exec-1][DependencyManagerSyncImpl:85] Dependency manager sync timeout after waiting 60s

Environment

  • Liferay DXP 7.2, 7.3

Resolution

  • DependencyManagerSyncImpl class was introduced on 7.2 (LPS-102056) to apply ComponentExecutorFactory for DM in order to enable concurrent activation.
    • The DependencyManagerSyncImpl waits, by default, 60 seconds for the initialization tasks to be completed.
    • If after that time they haven't finished the previous mentioned warning will appear.
  • The following approaches can be followed (only if the message appears constantly and no other time consuming issues have been detected during the startup):
    • In order to increase the default time the following property can be configured in the portal-ext.properties file: module.framework.properties.dependency.manager.sync.timeout=60
    • The component activation thread pool can be directly disabled using, also in portal-ext.properties, the following property: module.framework.properties.dependency.manager.thread.pool.enabled=false This last option will prevent the WARN message from appearing but can lead to a not optimized startup since the activation will be done serially. It should be used only as a workaround until an appropriate value is found for the timeout.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base