<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <title>Liferay 7.4 Ehcache configuration</title>
  <link rel="self" href="https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=122060215" />
  <subtitle>Liferay 7.4 Ehcache configuration</subtitle>
  <id>https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&amp;threadId=122060215</id>
  <updated>2026-04-05T20:17:29Z</updated>
  <dc:date>2026-04-05T20:17:29Z</dc:date>
  <entry>
    <title>RE: Liferay 7.4 Ehcache configuration</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122090937" />
    <author>
      <name>Nejati Unl</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122090937</id>
    <updated>2023-10-13T16:48:00Z</updated>
    <published>2023-10-13T16:29:18Z</published>
    <summary type="html">&lt;p&gt;This's solved for our side. We configured TCP-Unicast  for our
  cluster on AWS.&lt;/p&gt;</summary>
    <dc:creator>Nejati Unl</dc:creator>
    <dc:date>2023-10-13T16:29:18Z</dc:date>
  </entry>
  <entry>
    <title>RE: Liferay 7.4 Ehcache configuration</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122086362" />
    <author>
      <name>Zellact Icewane</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122086362</id>
    <updated>2023-10-13T16:07:02Z</updated>
    <published>2023-10-11T04:54:33Z</published>
    <summary type="html">&lt;p&gt;I'm also learning about the formula for this programming. You shared
  at the right time. It's great to have so much documentation&lt;/p&gt;</summary>
    <dc:creator>Zellact Icewane</dc:creator>
    <dc:date>2023-10-11T04:54:33Z</dc:date>
  </entry>
  <entry>
    <title>RE: RE: Liferay 7.4 Ehcache configuration</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122076234" />
    <author>
      <name>Nejati Unl</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122076234</id>
    <updated>2023-10-05T17:12:14Z</updated>
    <published>2023-10-05T16:06:22Z</published>
    <summary type="html">&lt;p&gt;Thanks for your time,&lt;br&gt;
  &lt;br&gt; While starting containers I can see these logs both servers, so
  means cluster.link is working. Is it right?&lt;br&gt;
  &lt;br&gt;
&lt;/p&gt;
&lt;pre&gt;
&lt;code&gt;GMS: address=282eb4ca2e02-5973, cluster=liferay-channel-transport-0, physical address=10.0.2.100:44856


GMS: address=control-channel-logic-name-dev02-dxp01, cluster=liferay-channel-control, physical address=10.0.2.100:38194
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;I'm using aws instances within same subnet, however do we need to
  configure TCP Unicast configuration for my cluster?&lt;br&gt;
  &lt;br&gt;  &lt;/p&gt;</summary>
    <dc:creator>Nejati Unl</dc:creator>
    <dc:date>2023-10-05T16:06:22Z</dc:date>
  </entry>
  <entry>
    <title>RE: RE: Liferay 7.4 Ehcache configuration</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122073767" />
    <author>
      <name>Olaf Kock</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122073767</id>
    <updated>2023-10-04T09:04:52Z</updated>
    <published>2023-10-04T09:04:51Z</published>
    <summary type="html">&lt;p&gt;I'm assuming that your servers don't find each other:&lt;/p&gt;
&lt;p&gt;Display of the user list is done through Elasticsearch, while the
  page is fueled by the database - which relies on the cache.&lt;/p&gt;
&lt;p&gt;You&lt;em&gt; should&lt;/em&gt;​​​​​​​ see messages in the log that both
  computers find each other (but in this case you likely don't)&lt;/p&gt;
&lt;p&gt;If I remember correctly, discovery is done through Multicast (unless
  you configure Unicast explicitly), and Multicast is often disabled in networks.&lt;/p&gt;</summary>
    <dc:creator>Olaf Kock</dc:creator>
    <dc:date>2023-10-04T09:04:51Z</dc:date>
  </entry>
  <entry>
    <title>RE: Liferay 7.4 Ehcache configuration</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122070899" />
    <author>
      <name>Nejati Unl</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122070899</id>
    <updated>2023-10-03T15:19:48Z</updated>
    <published>2023-10-03T08:17:51Z</published>
    <summary type="html">&lt;p&gt;Hi all,&lt;br&gt;
  &lt;br&gt; If I create a user from first server, it can reflect in the
  second server. However, when I updated a page and publish in first
  server, it didn't reflect to second server.&lt;br&gt;
  &lt;br&gt; Thanks for your help.&lt;/p&gt;</summary>
    <dc:creator>Nejati Unl</dc:creator>
    <dc:date>2023-10-03T08:17:51Z</dc:date>
  </entry>
  <entry>
    <title>Liferay 7.4 Ehcache configuration</title>
    <link rel="alternate" href="https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122060214" />
    <author>
      <name>Nejati Unl</name>
    </author>
    <id>https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&amp;messageId=122060214</id>
    <updated>2023-09-28T21:24:11Z</updated>
    <published>2023-09-27T13:49:07Z</published>
    <summary type="html">&lt;p&gt;Hi there,&lt;br&gt;
  &lt;br&gt; I'm using Liferay 7.4 with two servers, behind load balancer and 
  we'd like to use clustering mode. &lt;br&gt;
  &lt;br&gt;
  &lt;em&gt;
    &lt;code&gt;When we changed smth in the page, it didn't reflect to the
      secod server. &lt;br&gt;
      &lt;br&gt; Is there any missing point?&lt;/code&gt;
  &lt;/em&gt;
&lt;/p&gt;
&lt;p&gt;
  &lt;br&gt; We placed these configuration in our properties file.&lt;br&gt;
  &lt;br&gt; my portal-ext.properties file is ;&lt;/p&gt;
&lt;pre&gt;
&lt;code&gt;     ## Cluster Nodes Configuration
        
        cluster.link.enabled=true
        cluster.link.autodetect.address={{ POSTGRES_HOST }}:{{ POSTGRES_HOST_PORT }}

        ehcache.multi.vm.config.location=/ehcache/liferay-multi-vm.xml&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;I found the liferay-multi-vm.xml file from &lt;code&gt;Portal Cache -
    Impl.lpkg then mounted in our both servers.&lt;br&gt;
    &lt;br&gt; liferay-multi-vm.xml file;&lt;/code&gt;
  &lt;br&gt;  &lt;/p&gt;
&lt;pre&gt;
&lt;code&gt;&amp;lt;ehcache
	dynamicConfig=&amp;quot;true&amp;quot;
	monitoring=&amp;quot;off&amp;quot;
	name=&amp;quot;liferay-multi-vm&amp;quot;
	updateCheck=&amp;quot;false&amp;quot;
	xmlns:xsi=&amp;quot;http://www.w3.org/2001/XMLSchema-instance&amp;quot;
	xsi:noNamespaceSchemaLocation=&amp;quot;http://www.ehcache.org/ehcache.xsd&amp;quot;
&amp;gt;

	&amp;lt;!--
	Caches in this file can be clustered and are configured to be clustered.
	--&amp;gt;

	&amp;lt;defaultCache
		eternal=&amp;quot;false&amp;quot;
		maxElementsInMemory=&amp;quot;10000&amp;quot;
		overflowToDisk=&amp;quot;false&amp;quot;
		timeToIdleSeconds=&amp;quot;600&amp;quot;
	&amp;gt;
	&amp;lt;/defaultCache&amp;gt;&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;
  &lt;br&gt;
  &lt;br&gt; I'll appreciate very much your help here.&lt;br&gt;
  &lt;br&gt; Thanks!&lt;br&gt;
  &lt;br&gt;
  &lt;br&gt;  &lt;/p&gt;
&lt;p&gt; &lt;/p&gt;</summary>
    <dc:creator>Nejati Unl</dc:creator>
    <dc:date>2023-09-27T13:49:07Z</dc:date>
  </entry>
</feed>
