This content has been marked as final.
Show 5 replies
-
1. Re: JBAS-4766 Discussion thread
brian.stansberry Oct 3, 2007 5:55 PM (in response to brian.stansberry)Looks like client 94 also lost a session when node3 was stopped.
-
2. Re: JBAS-4766 Discussion thread
brian.stansberry Oct 3, 2007 6:48 PM (in response to brian.stansberry)The perf03 log is showing missing responses to data gravitation requests. Due to timeout. Dominik, can you change the buddy replication config in the jboss-web-cluster.sar/META-INF/jboss-service.xml and see what happens:
<buddyCommunicationTimeout>20000</buddyCommunicationTimeout>
We want 20 secs instead of 2 secs.
Manik, since this param drives the wait time for data gravitation, does it make sense to you that in general the value should be the same as SyncReplTimeout?
I'd thought it was only used for the group formation messages; even there 2 secs is probably too low. -
3. Re: JBAS-4766 Discussion thread
dpospisil Oct 4, 2007 4:41 AM (in response to brian.stansberry)"bstansberry@jboss.com" wrote:
Discussion of test failure reported in http://jira.jboss.com/jira/browse/JBAS-4766
At this point you got failures. The kill/restart of node0 went OK, but then when node1 was killed 2 of 100 sessions were lost.
Does that summarize it correctly?
Yes, that's correct. However, that's not the rule. During other test runs, sessions were lost even when first node failed. -
4. Re: JBAS-4766 Discussion thread
brian.stansberry Oct 4, 2007 10:37 AM (in response to brian.stansberry)Yep; I continued digging and found the issue discussed in my last post. That could crop up at any point.
-
5. Re: JBAS-4766 Discussion thread
brian.stansberry Oct 5, 2007 3:16 PM (in response to brian.stansberry)