Specifically, all cache server JVMs (storage-enabled cluster members) need to include See Changing the Default Unicast Port in Developing Applications with Oracle Coherence.Īpplications that use Oracle Coherence GoldenGate HotCache require an additional JARįile to certain JVM classpaths when upgrading from Coherence version 12.1. Lastly, ensure that the unicast port range is open for both UDP and TCP traffic and that the unicast listen port range is explicitly set rather then relying upon a system assigned ephemeral port. Solutions that require the use of a firewall between cluster members should ensure that the cluster port (7574) is open for both UDP and TCP for both multicast and unicast configurations as well as port 7 for Coherence TcpRing/IpMonitor death detection. See Running the Message Bus Test Utility and TCP Considerations in Administering Oracle Coherence. A message bus test utility is provided that can be used test TMB performance between network nodes. In addition, there should be very little network load difference between UDP and TCP. Most networks are already optimally configured for TCP and do not require Coherence-specific configuration. UDP is still used for cluster maintenance while TCP is used for workloads which may be more performance sensitive. The default protocol that is used between clustered data services has changed from UDP to TCP message bus (TMB). See Defining a Single Proxy Service Instance in Developing Remote Clients for Oracle Coherence. Extend clients that run on the same network as the proxy and use the Name service are no longer required to configure an address or a port, so long as they have an operational configuration which is compatible with the cluster. However, extend clients that rely on the Name service to find a proxy and rely on the previous default Name service port must be updated to use the new default. Proxy addresses that are explicitly configured are still used. The Name service now automatically uses the cluster port. See Specifying WKA Addresses in Developing Applications with Oracle Coherence. However, solutions that relied on the previous default port need to be updated accordingly. WKA addresses which contain an explicit port are still respected but it is recommended that the new form which does not include a port be used instead as it provides increased availability. See Specifying a Cluster Member Unicast Address and Port in Developing Applications with Oracle Coherence. For most use cases, unicast ports do not need to be explicitly configured. However, solutions that relied on the previous default ports need to be updated accordingly. Unicast ports that are explicitly configured are still used. Unicast Ports are now automatically selected. See Specifying a Cluster's Multicast Address and Port in Developing Applications with Oracle Coherence. However, solutions that rely on the previous defaults need to be updated to use the new defaults. Addresses and ports that are explicitly configured are still used. The enhancements include:Ĭoherence now uses port 7574 as the default cluster port for multicast communication and 239.192.0.0 as the default address. Significant enhancements have been made to simplify the way Coherence addresses and ports are configured and may require updates to your solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |