Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

How can I resolve "Unable to get portal cache manager MULTI_VM_PORTAL_CACHE_MANAGER" errors?

Written By

Madeleine Clay

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

  • I am seeing the following error in my clustered environment:
com.liferay.portal.kernel.messaging.MessageListenerException: java.lang.IllegalStateException: Unable to get portal cache manager MULTI_VM_PORTAL_CACHE_MANAGER

 

Environment

  • DXP 7.2
  • DXP 7.3

Resolution

  • LPS-123495 prevents the errors from showing up in the logs, but the errors themselves can be safely ignored.
  • LPS-123495 is available in 7.2 fp-12 and above, and in 7.3 fp-1 and above, or it can be requested as a hotfix at your current patching level.

Additional Information

  • The errors that LPS-123495 prevents occur because nodeA sends messages to nodeB before nodeB has fully started up. The messages from nodeA are telling nodeB to modify its cache. However, at this point, nodeB has not initialized its cache yet.
  • The only behavioral change resulting from the fix to LPS-123495 is that now the exception is not thrown.
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?