]
Galder Zamarreno closed JBAS-5536.
----------------------------------
Fix Version/s: JBossAS-5.0.0.Beta4
JBossAS-4.2.2.GA
Resolution: Duplicate Issue
UnifiedInvokerHAProxy replicants are not updated when other nodes
undeploy beans
--------------------------------------------------------------------------------
Key: JBAS-5536
URL:
http://jira.jboss.com/jira/browse/JBAS-5536
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Clustering, Remoting
Affects Versions: JBossAS-5.0.0.Beta3, JBossAS-4.2.1.GA
Reporter: Galder Zamarreno
Assigned To: Galder Zamarreno
Priority: Critical
Fix For: JBossAS-5.0.0.Beta4, JBossAS-4.2.2.GA
We have a big regression at out hands. When we moved to unified
invokers, we lost the ability for home/bean proxies to be updated
when another node undeploys a bean. Why?
ProxyFactoryHA.replicantsChanged looks something like this
(the trace logs were added by me during debugging):
public synchronized void replicantsChanged (String key,
List newReplicants,
int newReplicantsViewId)
{
try
{
if (homeInvoker instanceof InvokerProxyHA)
{
if (log.isTraceEnabled())
{
log.trace("Updating home proxy with new replicants " +
target.getReplicants() + ", view=" + target.getCurrentViewId ());
}
((InvokerProxyHA)homeInvoker).updateClusterInfo (target.getReplicants(),
target.getCurrentViewId ());
}
if (beanInvoker instanceof InvokerProxyHA)
{
if (log.isTraceEnabled())
{
log.trace("Updating bean proxy with new replicants " +
target.getReplicants() + ", view=" + target.getCurrentViewId ());
}
((InvokerProxyHA)beanInvoker).updateClusterInfo (target.getReplicants(),
target.getCurrentViewId ());
}
log.debug ("Rebinding in JNDI... " + key);
rebindHomeProxy ();
}
catch (Exception none)
{
log.debug (none);
}
}
UnifiedInvokerHAProxy *does not* implement InvokerProxyHA, so unified invoker ha
proxies will never have their replicants updated.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: