Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Elements are Missing from my JDBC_Ping Clustered Environment

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

  • Elements are missing from my JDBC_Ping clustered environment, and I'm seeing Unsupported template manager ftl errors in the logs.
  • When I disable clustering, the elements are all present.

Environment

  • DXP 7.2

Resolution

  • It may be that the nodes are unable to detect each other over the default autodetect address.
  • In portal-ext.properties, set cluster.link.autodetect.address equal to the portal server or your local gateway.
## Cluster Link
#
# Set this property to autodetect the default outgoing IP address so that
# JGroups can bind to it. The property must point to an address that is
# accessible to the portal server, www.google.com, or your local gateway.
#
# Env: LIFERAY_CLUSTER_PERIOD_LINK_PERIOD_AUTODETECT_PERIOD_ADDRESS
#
cluster.link.autodetect.address=www.google.com:80

Additional Information

  • cluster.link.autodetect.address is used to point JGroups that the Liferay node is using to an address where it can detect other Liferay nodes.
  • In most cases, Liferay nodes have Internet access, so the default value of pointing to google.com is sufficient.
  • However, if the cluster can't use google.com to detect other Liferay nodes (for example, if it doesn't have internet access), this property can be updated to point the nodes toward the portal server or your local gateway.

 

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