[jboss-user] [Clustering/JBoss] - Re: purgeDeadMembers Failing - what is the cause?

[jboss_cody]

The release is 4.2.1 GA.

The sessions, are just a "session.getId()" call within a jsp page.

When I said "sessions", I may have misspoken. I have a sample application that displays the sessionId inside a .jsp.  It also displays the name of of the node, and it has a counter of how many hits that it has taken. 

Heres an example from the jsp:

  | session ID: y20PI8Ro-nlJavY5zjNXaQ**.jboss11
  | 
  | You have hit this page 1 times
  | 
  | (Link to this Page)
  | 

I start 2 nodes. 
I enter my url and I get sent to node1.
Then I stop node1, and click a link that refreshes the current page. (basically a refresh) 

Once I do this, the sessionId appears(which is good), with the same node name(which is bad, because node1 is now dead.)

The counter resets(which is also bad, it shoud have incremented).

Then I refresh again, and this time the sessionId is the same(which is good), the node name is different(which is the fail-over occurring-good)

The counter increments (which is good, but the count is 1 less than what it is supposed to be).

I see in the logs that the DistributedReplicantManager is unable to remove the dead members.

What would make this happen? Is there a configuration that I'm missing?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4101932#4101932

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4101932