After LC ES Server hardening, we noticed that auto-update is not working for To Do list, session message and new task notification toast message. Before server hardening, all of them are still working fine.
Does anyone know why auto-update is not working after server hardening? Is there any specific port numbers which need to be enabled/opened to solve this issue?
FYI, we also noticed that some RemoteEventClient error messages occur many times in jboss server.log file as the following:
2008-01-10 15:26:19,398 INFO [com.adobe.livecycle.remoteevents.client.RemoteEventClient] Client JGroup initialization failed to connect to service JGroup. Service JGroup initialization may not be complete, retrying...
2008-01-10 15:26:20,414 INFO [com.adobe.livecycle.remoteevents.client.RemoteEventClient] com.adobe.livecycle.remoteevents.client.RemoteEventClient$RemoteEventReceiver using JGroups config UDP(bind_addr=10.77.250.248;mcast_addr=18.104.22.168;mcast_port=42707;ip_ttl=8):PING(timeout=3000;num_initial_members=6):FD(timeout=3000):VERIFY_SUSPECT(timeout=1500):pbcast.NAKACK(gc_lag=10;retransmit_timeout=600,1200,2400,4800):UNICAST(timeout=600,1200,2400,4800):pbcast.STABLE(desired_avg_gossip=10000):FRAG:pbcast.GMS(join_timeout=5000;join_retry_timeout=2000;shun=true;print_local_addr=true):VIEW_ENFORCER
First off can you explain what "Server Hardening is all about"?
Secondly, this looks like the JGroups isn't starting up correctly. Have you locked (shutdown) ports which applications can't use? You can modify the setup of JGroups by exporting the global workspace settings via the AdminUI.
JGroups is an open source project that allows processes to send messages to one another. LiveCycle data services uses it for its messaging implementation (basically it configures the server to multicast messages to all the listening clients...even in a clustered environment across different LAN/WAN).
In most cases the default configuration will work fine, the problem is that if you are running a firewall on the server (or your local machine...i.e. windows firewall) the ports that JGroups uses for its communications can be blocked. In a local environment its easy enough to disable windows firewall and bounce your server to get things working.
In a production environment you need to open the ports that JGroups is using. These settings are in the Global Administration settings (as mentioned by WorkspaceUser above). If you export it and look at the JChannelConnectionProperties you'll see the ports its using and you can set your firewall to allow communication to those ports.
No you don't need that to be set to your IP. The bind_addr will be set at runtime to your IP address. The mcast_addr is set to the correct reserved range for your OS (I think 224 on Unix and maybe 235 on Windows...guessing there, not 100% sure).
Probably not the problem, but related for anyone searching: my To Do list does not get updated for groups that are part of an enterprise domain. I was told this is a known issue as well and slated to be fixed in the next SP. I created a local group with the enterprise group as a member and that works.