On Artemis... We have some tests that we validate through topology and asserting server's bindings... Can you do the same on your tests.. or you won't have such APIs available?
On Wed, Sep 23, 2015 at 10:00 AM, Jeff Mesnil <[email protected]> wrote: > Hi, > > On Tue, Sep 15, 2015 at 5:35 PM, Jeff Mesnil <[email protected]> wrote: > > On Tue, Sep 15, 2015 at 3:11 PM, Clebert Suconic > > <[email protected]> wrote: > >> The ClusterConnectionControl will get the topology from the > >> ClusterConnection that will get activated only after the server is > >> activated (start method called). > >> > >> As a result this method is only available at the running server. > > > > I get an empty nodes when I call it on the live server after starting > > both servers. > > Why is there a discrepancy between the number of nodes in > > #getTopology() and #getNodes()? > > We have some clustering tests for our app server using Artemis. > We noticed frequent failures in these tests because the cluster of > Artemis nodes is not formed in timely fashion. > We use JGroups replication for our cluster communication. Usually, the > tests fails because the cluster is not formed before we start testing > things. > > What is the correct way to ascertain that a cluster is formed? > Ideally I want to know how many nodes are in the clusters and how many > of them are live. > > Please note that increasing a timeout after servers are started and > before tests are exercised is not enough. There are some cases where > the cluster is never formed at all (when playing with failover and > tailback). But to test this use case, I first must be able to check > the cluster topology in a reliable way. > > thanks, > jeff > > -- > Jeff Mesnil > [email protected] > http://jmesnil.net/weblog/ > -- Clebert Suconic
