Chapter 17: Clustering Replace 192.168.23.2 with your own IP address. Note that the highlighted line is the TCP port on which the Apache Tribes data replication mechanism listens for incoming session update information. Because all three of the Tomcat instances are running on the same physical machines, the port must be different for machine1, machine2, and machine3. The following table shows the port assignments that you need to use. Make sure you configure them properly in the corresponding server.xmlfile. Instance Name tcpListenPort machine1 4200 machine2 4300 machine3 4400 Binding to a Specific Adapter on Multi-Homed Machines Another parameter to be careful about is the bindattribute of the element. This bind attribute is highlighted in bold within the preceding configuration listing. This attribute selects the physical network interface to use on machines that have more than one network adapter called multi-homed machines. If you have only one network adapter, this parameter is typically not necessary. However, because of the way operating systems tend to create virtual network adapters for high-speed links such as IEEE 1394 Firewire, specifying this parameter prevents surprises. The address specified should be the IP address of the specific adapter you want to use. Configuring the Element The following table shows the attributes available for the element. Attribute Name Description Default className The implementation Java class for the cluster manager. Currently, only org.apache.catalina.ha.tcp .SimpleTcpClusteris available. Table continued on following page
For high quality website hosting services please check java web hosting website.
This entry was posted
on Wednesday, November 18th, 2009 at 12:42 pm and is filed under tomcat.
You can follow any responses to this entry through the RSS 2.0 feed.
Responses are currently closed, but you can trackback from your own site.