Page History
...
It should be considered if this overhead is worth the added fail-safe functionality that it brings. If Session Replication is not used, and a node fails, a user’s session will be destroyed, but they'll be able to log in to another node to continue their work.
| Anchor | ||||
|---|---|---|---|---|
|
Modifications to web.xml
The text “<distributable/>” needs to be added to the web.xml file on each node underneath the “<webapp>” line. For example:
...
| Code Block | ||
|---|---|---|
| ||
<web-app>
<distributable/>
<!-- System Event and Debug classes -->
<listener>
<listener-class>com.hof.servlet.SysSessionListener</listener-class>
</listener>
|
| Anchor | ||
|---|---|---|
|
|
Modifications to server.xml
Changes need to be made to the server.xml file in the Yellowfin/appserver/conf directory.
Add the additional XML entry within the “<host>” XML block.
| Code Block | ||
|---|---|---|
| ||
<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster"/> |
The IP address “228.0.0.4” is a multicast address that session replication messages will be received on. This does not need to be modified, but a Linux/Unix server may need to register a valid multicast route to receive broadcasts on this address. This can be done by running the following command on the console:
| Code Block | ||
|---|---|---|
| ||
sudo route add -net 224.0.0.0 netmask 224.0.0.0 dev eth0 |
This syntax may be different for different flavours of Linux or Unnis. This example uses “eth0” as the network device that will be used for this route.
| Anchor | ||||
|---|---|---|---|---|
|
Modifications to ROOT.xml
...