Issue: In a network environment with non-Ephesoft servers running java and Tomcat, if the multicastGroupAddress and the multicastGroupPort are set to default values on a non-Ephesoft server, you may see connection attempts in the non-Ephesoft server logs.

Root Cause: Most applications, including Ephesoft leave the defaults for these values of the RMI ehcache system out of convenience. This can cause to applications such as Ephesoft finding the open listening port on another server and attempting to communicate with it. Given that we would not share any packages, the connection fails, but it will leave requests in the logs of the other application.

Solution: Changing the multicastGroupAddress and the multicastGroupPort in Ephesoft will resolve the issue.

In the file <Ephesoft install directory>\Application\WEB-INF\classes\META-INF\dcma-data-access\dcma-ehcache.xml you will find the following values:<cacheManagerPeerProviderFactory
class=”net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory”
properties=”peerDiscovery=automatic,multicastGroupAddress=230.0.0.1,multicastGroupPort=4446″ />

You will want to change the multicastGroupAddress to a value between 229.0.0.1 to 239.255.255.255. However this needs to match on all Ephesoft instances on the network

You will also want to change the multicastGroupPort. This can be set to any unused port in windows, but again, it must be the same on all Ephesoft servers on the network.

Restarting Ephesoft after making these changes is necessary.

Update: Starting with Ephesoft 4.0.4.0, these values will be set to non-default values out of the box so this issue will not appear anymore.