Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

"Service "com.liferay.portal.kernel.cache.MultiVMPool" is unavailable" errors in the logs during startup

Written By

Anna Zombori-Suszter

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 error can be seen in the logs multiple times during server startup
ERROR [Start Level: Equinox Container: 30e307ea-2db2-001b-1b24-8fe7a9e210b3][ServiceProxyFactory:265] Service "com.liferay.portal.kernel.cache.MultiVMPool" is unavailable in 60000 milliseconds while setting field "_multiVMPool" for class "com.liferay.portal.kernel.cache.MultiVMPoolUtil", will retry...

Environment

  • Liferay DXP 7.0
  • Liferay DXP 7.1

Resolution

The error message itself indicates that there is no bundle providing the service com.liferay.portal.kernel.cache.MultiVMPool.

Based on previously reported cases, currently the following scenarios are known when the error may happen, other than the problem being a customization related issue:

  1. The application server was forcefully shut down instead of gracefully. For example, closing the Tomcat console by clicking the close button without calling shutdown.sh, or killing the process through the command line and restart the server without cleaning up the following folders:
    • osgi/state
    • {liferay_home}/work
    • {tomcat}/temp
    • {tomcat}/work
  2. An incompatible portal-kernel.jar is used which can happen if the portal-kernel.jar gets replaced, for example during development.
  3. Incorrect cluster settings. 

Disclaimer: It is possible that there are different root causes for this error, the above reasons are the ones that we have encountered so far. 

As a workaround, deleting the osgi/state folder can also resolve the problem temporarily.

Additional Information

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?