Null Values for PortalInetSocketAddress and PortalProtocol for Cluster Nodes
Written By
Daniel Carrillo Broeder
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
- When running a Groovy script to check cluster formation, the output shows "null" for
PortalInetSocketAddress and PortalProtocol for some nodes.
Environment
- DXP 7.4
- Quarterly Releases
Resolution
- This behavior is expected when not all cluster nodes have been accessed through a web browser, which prevents the "Updated cluster node {...}" event from being generated.
- To verify this, enable cluster debug logging (Control Panel > System Settings > Infrastructure > Cluster Executor > Enabled debug), restart all nodes, and check the logs for cluster events.
-
To fix the issue:
- Access each node in the cluster via a web browser and check logs to verify the "Updated cluster node" event.
- If the issue persists try to explicitly set the following properties in
portal-ext.properties on each node:
portal.instance.protocol=<protocol>
portal.instance.inet.socket.address=<ip>:<port>
Did this article resolve your issue ?