D4Science Infrastructure

this activity cannot be performed as the HTTP Session cannot be transparently brought on the other instance (due to the fact that we applying the required change on the ASL Session didn't work properly)

I did add the tomcat and Liferay cluster configurations on preprod1 and preprod2. However some firewall is blocking the Liferay communication between the 2 nodes (146.48.122.240 and 146.48.122.143)

13:14:19,271 DEBUG [Multicast keep-alive Heartbeat Receiver thread-2][MulticastRMICacheManagerPeerProvider:39] Unable to lookup remote cache peer for //146.48.122.240:60176/com.liferay.portlet.dynamicdatamapping.model.impl.DDMTemplateImpl. Removing from peer list. Cause was: Exception creating connection to: 146.48.122.240; nested exception is: _    java.net.NoRouteToHostException: No route to host [Sanitized]


.orm.FinderCache.com.liferay.sync.model.impl.SyncDLObjectImpl. Removing from peer list. Cause was: Exception creating connection to: 146.48.122.143; nested exception is: _ java.net.NoRouteToHostException: No route to host [Sanitized]
13:14:57,740 DEBUG [Multicast keep-alive Heartbeat Receiver thread-1][MulticastKeepaliveHeartbeatReceiver:48] Aborting processing of rmiUrls since failed to add rmiUrl: //146.48.122.143:59670/com.liferay.portlet.announcements.model.impl.AnnouncementsFlagImpl
13:14:57,740 DEBUG [Multicast keep-alive Heartbeat Receiver thread-3][RMICacheManagerPeerProvider:48] Lookup URL //146.48.122.143:59214/com.liferay.portal.kernel.template.TemplateResourceLoader.ftl
13:14:57,740 DEBUG [Multicast keep-alive Heartbeat Receiver thread-2][MulticastRMICacheManagerPeerProvider:39] Unable to lookup remote cache peer for //146.48.122.143:59670/com.liferay.portlet.dynamicdatamapping.model.impl.DDMTemplateImpl. Removing from peer list. Cause was: Exception creating connection to: 146.48.122.143; nested exception is: _    java.net.NoRouteToHostException: No route to host [Sanitized]
13:14:57,740 DEBUG [Multicast keep-alive Heartbeat Receiver thread-4][MulticastKeepaliveHeartbeatReceiver:48] Aborting processing of rmiUrls since failed to add rmiUrl: //146.48.122.143:59214/com.liferay.portal.kernel.dao.orm.FinderCache.com.liferay.sync.model.impl.SyncDLObjectImpl
13:14:57,740 DEBUG [Multicast keep-alive Heartbeat Receiver thread-2][MulticastKeepaliveHeartbeatReceiver:48] Aborting processing of rmiUrls since failed to add rmiUrl: //146.48.122.143:59670/com.liferay.portlet.dynamicdatamapping.model.impl.DDMTemplateImpl
13:14:57,740 DEBUG [Multicast keep-alive Heartbeat Receiver thread-3][MulticastRMICacheManagerPeerProvider:39] Unable to lookup remote cache peer for //146.48.122.143:59214/com.liferay.portal.kernel.template.TemplateResourceLoader.ftl. Removing from peer list. Cause was: Exception creating connection to: 146.48.122.143; nested exception is: _    java.net.NoRouteToHostException: No route to host [Sanitized]
13:14:57,741 DEBUG [Multicast keep-alive Heartbeat Receiver thread-3][MulticastKeepaliveHeartbeatReceiver:48] Aborting processing of rmiUrls since failed to add rmiUrl: //146.48.122.143:59214/com.liferay.portal.kernel.template.TemplateResourceLoader.ftl

The nodes need to communicate via RMI too. Now that traffic is permitted. I changed the firewall rules both on preproduction and production.

thanks, now the 2 preprod nodes can communicate correctly.