ehcache multicast error in system with no network connections

Issue Description

A customer needed to install JasperReports Server on a machine with no external network connections, a host only adapter that does not allow multi-cast traffic. This caused JRS to fail on startup with error:

2015-11-13 02:51:15,637 ERROR MulticastRMICacheManagerPeerProvider,localhost-startStop-1:98 - Error starting heartbeat. Error was: No such device java.net.SocketException: No such device

Resolution

Our Ehcache related files have a configuration like this:

<cacheManagerPeerProviderFactory class="net.sf.ehcache.distribution.RMICacheManagerPeerProviderFactory"properties="peerDiscovery=automatic,multicastGroupAddress=228.0.0.1,multicastGroupPort=4446,timeToLive=1"/>

This configuration is used to broadcast messages in clustered environment and it is assigning 228.0.0.1 as the multicast address. If you cannot "ping 228.0.0.1", which you can't if no network connection, then try setting peerDiscovery to manual instead of automatic, like:

peerDiscovery=manual,multicas...

This needs to be done in four files within WEB-INF: engine-ehcache.xml, olap-ehcache.xml, ehcache.xml, and ehcache_hibernate.xml.

Ref. Case 00064684