Liferay 7.1 ga1 : Unicast Over TCPLiferay 7.1 ga1 : Unicast Over TCPhttps://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=1147528262024-03-29T05:30:04Z2024-03-29T05:30:04ZRE: Liferay 7.1 ga1 : Unicast Over TCPAndrew Jardinehttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1148335362019-08-21T13:23:16Z2019-08-21T13:23:16ZThe caching that happens as part of a cluster config doesn't apply to the js, CSS, etc. It is applicable to the features that use ehcache such as the entity cache. Simplest test is this -1. Go to node 1 in your browser2. In a separate browser go to the same page, on node 23. On node 1 add a portlet to the page4. On node 2, refresh the page. If your cluster is working, then you should see the portlet on node 2 meaning the entity (layout) update on node 1 sent a message to node 2 and the cached record for that layout was purged. So when you refreshed node 2, the 'latest' version was cached after being pulled from the database.But if you don't see messages in your log during startup, the GMS output and references on the master node stating Accepted view when the second node is started, then it's probably node enabled. Andrew Jardine2019-08-21T13:23:16ZRE: Liferay 7.1 ga1 : Unicast Over TCPMayursinh Vaghelahttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1148331962019-08-21T13:08:29Z2019-08-21T13:08:29Z<strong><strong>Jardin thanks,</strong></strong><br />I have tried with upgradation process from 7.1 ga1 to ga3.check the below step<br /><ol style="list-style: decimal outside;" start="1"><li>Upgrade ga1 database using upgradation tool.(added all property that i define in ga1).<ol style="list-style: decimal outside;" start="1"><li>when i use verify it display some APIs that upgraded brtween this releases.</li></ol></li><li>Add all custom portlets in modules and war(deploy all portlets) and point to new database and portal properties.</li></ol>it look like all function are working. Even portal-ext file has been picked up.<br />Another question is : How i can test js,css cache working in cluster env.??Mayursinh Vaghela2019-08-21T13:08:29ZRE: Liferay 7.1 ga1 : Unicast Over TCPAndrew Jardinehttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1148316392019-08-21T12:03:44Z2019-08-21T12:03:44ZYeah, I figured it was a long shot and as I said, I don't think that actually fixed my issue but rather it was more of a coincidence that I did that and everything started working. For your question about dependencies, well, it all depends I suppose. Let's say for example you are using the journal-api and between the GA release there are API updates that are made that affect your code. If you can't use the older version then you would need to go through and update all of your versions everywhere you referenced it versus only having to make that change in one place. Really, it's a best practice that can make your life a lot easier. I recently upgraded a project that have about 80 modules and believe me, going through 80 build.gradle files to check them all sucked. Back to your problem though, are you sure your portal-ext is being picked up? Some things to try next.<br />1. When the portal is up and running, use the Server Administrator section in the control panel to check the value of the cluster.link.enabled property to make sure it is showing as true.2. Check the value of liferay.home (again in the control panel) and make sure it is referencing the right location, if it is not, then it might not be reading your portal-ext overrides3. Set a breakpoint where the cluster check is performed (during starting) and use your debugger to make sure that the result of the read operation returns the same result you have set in your portal-ext.. and maybe let us know what you find.Andrew Jardine2019-08-21T12:03:44ZRE: Liferay 7.1 ga1 : Unicast Over TCPMayursinh Vaghelahttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1148294392019-08-21T11:10:30Z2019-08-21T11:10:30Z<strong>Hi Andrew Jardin</strong><br />Removing lear osgi/state, LIFERAY_HOME/work, TOMCAT_HOME/work, TOMCAT_HOME/temp, and all not working with 7.1 GA1. Do i really need to update all the dependancy even when i upgrade from 7.1 ga1 to 7.1 ga3???Thanks and Regards Mayursinh VaghelaMayursinh Vaghela2019-08-21T11:10:30ZRE: Liferay 7.1 ga1 : Unicast Over TCPAndrew Jardinehttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1148020422019-08-19T14:22:21Z2019-08-19T14:22:21ZHi Mayursinh,I had a really bizarre experience last week that I still can't explain but I thought I would share here in case you are experiencing the same thing. In my case the symptoms were similar to what you describe, but I was working with 7.2GA1. For some reason, the portal-ext changes I was making (in particular the cluster.link.enabled setting), what not being picked up correctly during startup. When I checked the property post startup it was reporting the correct value, a value of true, but when I set a breakpoint in the LR source to check it right at the beginning of startup it was reporting false. Now, in my case, which I cannot explain to be honest, all I had to do was clear osgi/state, LIFERAY_HOME/work, TOMCAT_HOME/work, TOMCAT_HOME/temp, not of which should matter for properties, I know, but once I did that and restarted, the property started getting picked up correctly. Again, still can't explain it, but it got me past the hurdle and started showing the GMS logging output. With all that said, definitely upgrade to 7.2! With Liferay's releases coming closer together now (1 year apart in place of 3 or 4) it makes upgrading so much simpler. If you also do this in conjunction with the BOM files for dependencies, upgrades, or at least testing out an upgrade, takes no time at all<br /> (if you are unfamiliar, Here are the docs: <a href="https://portal.liferay.dev/docs/7-1/tutorials/-/knowledge_base/t/managing-the-target-platform-for-liferay-workspace">https://portal.liferay.dev/docs/7-1/tutorials/-/knowledge_base/t/managing-the-target-platform-for-liferay-workspace</a> and David just wrote a great blog post on it -- <a href="https://liferay.dev/blogs/-/blogs/liferay-workspace-distribution-bundles">https://liferay.dev/blogs/-/blogs/liferay-workspace-distribution-bundles</a>) Andrew Jardine2019-08-19T14:22:21ZRE: Liferay 7.1 ga1 : Unicast Over TCPOlaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1147999962019-08-19T11:30:51Z2019-08-19T11:30:51Z<div class="quote-title">Mayursinh Vaghela:</div><blockquote><br />ok, Thanks to both of you.so, I need to use the upgradation tool as suggested in Liferay 7.1 docs. Then need to deploy all portlets and it will be fine right??</blockquote>"...it will be fine": It depends on the customizations that you've done. If you've done them with maintenance minimization in mind: Most likely yes. If you've changed the implementation, bypassing the API: Prepare for some work.Olaf Kock2019-08-19T11:30:51ZRE: Liferay 7.1 ga1 : Unicast Over TCPMayursinh Vaghelahttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1147996592019-08-19T11:23:19Z2019-08-19T11:23:19Zok, Thanks to both of you.so, I need to use the upgradation tool as suggested in Liferay 7.1 docs. Then need to deploy all portlets and it will be fine right??Mayursinh Vaghela2019-08-19T11:23:19ZRE: Liferay 7.1 ga1 : Unicast Over TCPOlaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1147991682019-08-19T07:54:16Z2019-08-19T07:54:16Z<div class="quote-title">Mayursinh Vaghela:</div><blockquote><br />Development is already done in ga1. I have used ga3 for testing purpose. <br /><br /></blockquote>That's the reason why any development should use the quite stable APIs, and not modify implementation directly: You'll have an easy way updating to the next release. This includes security issues, but also bugs like the one that you seem to have discovered. Short: If you limit yourself to exactly one GA version, you'll exclude yourself from future updates - and that includes security issues. You'd have to patch your version yourself.<br />Don't do that, move your code forward to GA3 (and then, after release, prepare to move to 7.2.x, for the same reasons. If you find that you're changing a lot of Liferay's implementation (through ext or direct patches of modules): Try to find a way to do so in a less intrusive way.Olaf Kock2019-08-19T07:54:16ZRE: Liferay 7.1 ga1 : Unicast Over TCPMayursinh Vaghelahttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1147984352019-08-19T05:58:29Z2019-08-19T05:58:29ZHi <strong>Juan Gonzalez,</strong><br />Development is already done in ga1. I have used ga3 for testing purpose. <br />Thanks and Regards<br />Mayursinh VaghelaMayursinh Vaghela2019-08-19T05:58:29ZRE: Liferay 7.1 ga1 : Unicast Over TCPJuan Gonzalezhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1147928302019-08-17T09:59:34Z2019-08-17T09:59:34ZSo, if it works in latest GA version, then what's the problem? Juan Gonzalez2019-08-17T09:59:34ZLiferay 7.1 ga1 : Unicast Over TCPMayursinh Vaghelahttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1147528252019-08-14T06:21:39Z2019-08-14T06:21:39ZHi Everyone,<br />I have working on clustering in Liferay 7.1 ga1 portal. Other things are working fine like session replication, shared database and document library, standalone Elastic search etcc..<br /><br />But I have an issue with below property. when I add it in ga1 then it does not start GMS server. But when I add it in newly downloaded ga3 server then it's working fine.<br />cluster.link.enabled=true<br />I have added below configuration in different files<br /><ol sty