NAKACK "message <ip::messageID> not found in retransmission table" where messageID is too high
Environment
- JBoss Enterprise Application Platform (EAP)
- 5.0.x
- 5.1
Issue
- Message similar to the following occurs in the logs
WARN [org.jgroups.protocols.pbcast.NAKACK] (OOB-831,<local_ip>:<port>) (requester=<requester_ip>:<port>, local_addr=<local_ip>:<port>) message <local_ip>:<port>::<message_id> not found in retransmission table of <local_ip>:<port>:
[10 : 13 (4) (size=4, missing=0, highest stability=10)]
Resolution
- This issue is fixed in EAP 5.1.1
- There is a support patch [1] available for EAP 5.1.0
- As a workaround, pending deployment of a patch, to get the cluster functional again after the bug is triggered, restart the node listed in the NAKACK warning log as "requester=X.X.X.X"
[1] https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?softwareId=5703
Root Cause
Diagnostic Steps
- If the messageID in any log is higher than the range of current messages in that log or the requested messages begin with 1, this is the issue.
For example, with the following log, a messageID greater than 13 indicates this issue
[10 : 13 (4) (size=4, missing=0, highest stability=10)]
- If there are no logs with a higher messageID and the requested message IDs begin slightly below the highest stability, see NAKACK "message <:messageid> not found in retransmission table" where messageID is too low
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments