[jboss-jira] [JBoss JIRA] Updated: (JGRP-455) Problem with retransmission: message not found
Bela Ban (JIRA)
jira-events at lists.jboss.org
Tue Apr 3 07:40:58 EDT 2007
[ http://jira.jboss.com/jira/browse/JGRP-455?page=all ]
Bela Ban updated JGRP-455:
--------------------------
Attachment: tmp2.txt
tmp2.txt shows that message 10.68.0.33:33814::66521 was not found in sent msgs [66632 - 68191]. However, stability shows that the last stability message
10: 10.68.0.33:33814: [66520 : 66520 (68190)],
purged messages with seqnos less than 66520, so seqno 66521 should have been found !
The question is why were sent_msgs purged to 66632 ?
> Problem with retransmission: message not found
> ----------------------------------------------
>
> Key: JGRP-455
> URL: http://jira.jboss.com/jira/browse/JGRP-455
> Project: JGroups
> Issue Type: Bug
> Affects Versions: 2.4.1 SP1
> Reporter: Bela Ban
> Assigned To: Bela Ban
> Priority: Critical
> Fix For: 2.5
>
> Attachments: tmp2.txt
>
>
> Sometimes a sender cannot find a message with a seqno as requested by a receiver. The seqno requested (47176) was already purged, sent_msgs: [48059 - 48090] (32)
> This could be either an issue in STABLE, which prematurely purges messages although not all members agreed on the highest seqnos seen, or NAKACK, which might incorrectly 'change' seqnos. Very hard to reproduce !
> Trace:
> 42032 [ERROR] [OOB Thread,perf,10.68.32.33:32968] NAKACK.handleXmitReq(): - (requester=10.68.28.33:33763, local_addr=10.68.32.33:32968) message 10.68.32.33:32968::47176 not found in sent msgs [48059 - 48090] (32)
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list