[
http://jira.jboss.com/jira/browse/JBCLUSTER-99?page=comments#action_12348948 ]
Tony Starks commented on JBCLUSTER-99:
--------------------------------------
>2006-03-20 16:05:18,669 ERROR
[org.jgroups.protocols.pbcast.NAKACK] (requester=1 72.16.130.57:41887,
local_addr=172.16.129.57:49802)
>message with seqno=3280 not found in sent_msgs ! sent_msgs=[1477 - 3503]
I am having the same problem as above mentioned with JGroups 4rc2(cannot as yet update
version to higher).
How can i fix it ?
Tips on how you resolved the above would be welcome.
4.0.4CR2 under Jbento load test numbers
---------------------------------------
Key: JBCLUSTER-99
URL:
http://jira.jboss.com/jira/browse/JBCLUSTER-99
Project: JBoss Clustering
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Reporter: Ben Wang
Assigned To: Brian Stansberry
Fix For: Q2Y6
Attachments: ResultsExtract.pdf
Time Spent: 1 day
Remaining Estimate: 0 minutes
I have used JBento to perform load test with 2 nodes cluster (dev02, dev03). It only
loads dev02 (so not load balanced yet). This is just a simple counter String test.
1. 10 clients with 10 ms sleep in between. The tps is 85. No error message produced
2. 50 client with 10ms sleep. Lots of errors:
2006-03-20 16:05:18,667 ERROR [org.jgroups.protocols.pbcast.NAKACK] (requester=1
72.16.130.57:41887, local_addr=172.16.129.57:49802) message with seqno=3277 not
found in sent_msgs ! sent_msgs=[1477 - 3502]
2006-03-20 16:05:18,668 ERROR [org.jgroups.protocols.pbcast.NAKACK] (requester=1
72.16.130.57:41887, local_addr=172.16.129.57:49802) message with seqno=3278 not
found in sent_msgs ! sent_msgs=[1477 - 3503]
2006-03-20 16:05:18,668 ERROR [org.jgroups.protocols.pbcast.NAKACK] (requester=1
72.16.130.57:41887, local_addr=172.16.129.57:49802) message with seqno=3279 not
found in sent_msgs ! sent_msgs=[1477 - 3503]
2006-03-20 16:05:18,669 ERROR [org.jgroups.protocols.pbcast.NAKACK] (requester=1
72.16.130.57:41887, local_addr=172.16.129.57:49802) message with seqno=3280 not
found in sent_msgs ! sent_msgs=[1477 - 3503]
The other node also ran into OOM as well.
--
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