| Summary | This article clarifies if the Orbix locator can be forced to use a load balancer if no load balancer has been associated with a POA |
|---|---|
| Article Number | 33020 |
| Environment | Orbix 6.3 All Supported Operating Systems |
| Question/Problem Description | Can the Orbix locator daemon be forced to use a load-balancer if no load-balancer has been associated with a POA? |
| Clarifying Information | Orbix uses the locator daemon to support replicated servers. If a persistent object is instantiated on a replicated server, its references contain the address of the locator daemon. The locator daemon is responsible for redirecting client requests on that object to one of the server’s replicas. Object persistence is always set by POA policies. Therefore, Orbix implements replication through registration of multiple instances, or replicas, of a POA, in a location domain’s implementation repository. This provides the necessary level of granularity without adding significant administrative overhead. POA replicas ensure continuous access to persistent objects; and the Orbix infrastructure is required only to monitor POA activity. |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution | When the locator daemon receives the locate request, it searches the IMR for the POA of the target object. If it finds that the POA is replicated (it has a load balancer associated to it) the locator daemon uses the load-balancing algorithm that is associated with the POA to determine which POA replica should handle the request. If the POA does not have a load-balancer associated to it the locator cannot be forced to use a load-balancer. |
| Workaround | |
| Notes | |
| Attachment |
| Created date: | 05 July 2012 |
|---|---|
| Last Modified: | 13 February 2013 |
| Last Published: | 05 July 2012 |
| First Published date: | 05 July 2012 |
#KnowledgeDocs
#Orbix
