[ http://jira.jboss.com/jira/browse/JBAS-1027?page=history ]

Scott M Stark updated JBAS-1027:
--------------------------------

      Assign To: Ovidiu Feodorov  (was: Scott M Stark)
    Description: 
SourceForge Submitter: mondrejko .
JBoss: 3.2.5
OS: Windows 2000, Redhat Linux, Solaris 8/9

HA-JNDI binding replicants not initialized properly when 
defining cluster using TCP as the base for the 
javagroups stack and disabling all auto-discovery.

I defined a cluster of two nodes using TCP and disabled 
node auto-discovery on both the server and client. 
Consequently, binding replicants must be explicitly 
shared among the cluster nodes. This appears to 
function properly for existing nodes when a new node 
joins the cluster (that is, the existing node replicants are 
updated for the bindings of the new node). However, 
the new node replicants are not updated with the 
bindings from the existing nodes. Therefore, when a 
client connects to this new node of the cluster, the 
client does not receive the propery replicants and load 
balancing and failover do not function properly.

A 3.2.5 patch to DistributedReplicationManagerImpl.java 
for a potential solution has been attached. With this 
patch, clustering with TCP and without auto-discovery 
works beautifully.

  was:
SourceForge Submitter: mondrejko .
JBoss: 3.2.5
OS: Windows 2000, Redhat Linux, Solaris 8/9

HA-JNDI binding replicants not initialized properly when 
defining cluster using TCP as the base for the 
javagroups stack and disabling all auto-discovery.

I defined a cluster of two nodes using TCP and disabled 
node auto-discovery on both the server and client. 
Consequently, binding replicants must be explicitly 
shared among the cluster nodes. This appears to 
function properly for existing nodes when a new node 
joins the cluster (that is, the existing node replicants are 
updated for the bindings of the new node). However, 
the new node replicants are not updated with the 
bindings from the existing nodes. Therefore, when a 
client connects to this new node of the cluster, the 
client does not receive the propery replicants and load 
balancing and failover do not function properly.

A 3.2.5 patch to DistributedReplicationManagerImpl.java 
for a potential solution has been attached. With this 
patch, clustering with TCP and without auto-discovery 
works beautifully.

    Environment: 
       Priority: Major  (was: Critical)

> HA-JNDI binding replicants not initialized properly
> ---------------------------------------------------
>
>          Key: JBAS-1027
>          URL: http://jira.jboss.com/jira/browse/JBAS-1027
>      Project: JBoss Application Server
>         Type: Bug
>   Components: Clustering
>     Versions: JBossAS-3.2.6 Final
>     Reporter: SourceForge User
>     Assignee: Ovidiu Feodorov

>
>
> SourceForge Submitter: mondrejko .
> JBoss: 3.2.5
> OS: Windows 2000, Redhat Linux, Solaris 8/9
> HA-JNDI binding replicants not initialized properly when 
> defining cluster using TCP as the base for the 
> javagroups stack and disabling all auto-discovery.
> I defined a cluster of two nodes using TCP and disabled 
> node auto-discovery on both the server and client. 
> Consequently, binding replicants must be explicitly 
> shared among the cluster nodes. This appears to 
> function properly for existing nodes when a new node 
> joins the cluster (that is, the existing node replicants are 
> updated for the bindings of the new node). However, 
> the new node replicants are not updated with the 
> bindings from the existing nodes. Therefore, when a 
> client connects to this new node of the cluster, the 
> client does not receive the propery replicants and load 
> balancing and failover do not function properly.
> A 3.2.5 patch to DistributedReplicationManagerImpl.java 
> for a potential solution has been attached. With this 
> patch, clustering with TCP and without auto-discovery 
> works beautifully.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.jboss.com/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to