[jboss-jira] [JBoss JIRA] Updated: (JBAS-5577) HA-JNDI load balancing of remote lookups after a local lookup failed

[Brian Stansberry (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBAS-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brian Stansberry updated JBAS-5577:
-----------------------------------

    Fix Version/s: Backlog


Assigning "Backlog" as Fix Version as that means this is a qualified issue, but we don't know when it will be done.

> HA-JNDI load balancing of remote lookups after a local lookup failed
> --------------------------------------------------------------------
>
>                 Key: JBAS-5577
>                 URL: https://jira.jboss.org/jira/browse/JBAS-5577
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Naming
>            Reporter: Galder Zamarreno
>            Assignee: Galder Zamarreno
>             Fix For: Backlog
>
>
> HA-JNDI load balancing only comes into play when talking to it remotely, 
> or when the HA-JNDI proxy in the server does not belong to the same 
> cluster as the target HA-JNDI proxy trying to get.
> Any other time, HA-JNDI tries to do a lookup locally and if not found, asks 
> the cluster. Now, out of those responses, HA-JNDI takes the first non null 
> and non exception one and returns that and hence multiple calls to HA-JNDI 
> can look as if they were not load balanced. 
> In order to see some kind of load balancing in this situation, HA-JNDI would 
> need to somehow be extended to keep track what was the last non local 
> response returned back to the client and take that potentially into account 
> when returning the next response. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira