Skip Headers

# Configuring a Packet Time-to-Live

Previous

Next

The packet time-to-live is the number of hops that session data packets can take before expiring. The default is 2. This allows for a hub and an interface card, and prevents the data packets from leaving the local network. If sessions are hosted on different local area networks (LANs) that are part of wide area network (WAN), or if a firewall configuration prevents it, the announcement sent by one session may not reach the other sessions in the coordinated cache. In this case, consult your network administrator for the correct time-to-live value.

Table: Coordinated Cache Support for Packet Time-to-Live Configuration summarizes which coordinated caches support packet time-to-live configuration.

Coordinated Cache Support for Packet Time-to-Live Configuration

Coordinated Cache | Using TopLink Workbench | Using Java
--- | --- | ---
JMS Coordinated Cache |  |
RMI Coordinated Cache |  |
CORBA Coordinated Cache |  |
Custom Coordinated Cache |  |

In addition to configuring packet time-to-live, you may also need to configure announcement delay (see "Configuring an Announcement Delay").