No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


Log Reference

AR500, AR510, and AR530 V200R007

This document supports all the logs of device, including the parameters, meaning, possible causes and solution.

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).



SOCKET/4/EXCEEDMAXQLEN:The number of messages in the asynchronous message queue was greater than the message upper limit. (Time=[ULONG], TaskName=[STRING], TaskId=[ULONG], SocketId=[ULONG], ErrorCode=[LONG])


The number of messages in the asynchronous message queue exceeded the defined upper limit.


Parameter Name Parameter Meaning
Time indicates the time when the log is generated.
TaskName indicates the task name.
TaskId indicates the task ID.
SocketId indicates the socket ID.
ErrorCode indicates the error code, that is, -8.

Possible Causes

Each asynchronous socket has a queue to receive messages. This log indicates that the message queue was full and no new message could be received. The cause is that the speed in which the CPU read messages was slower than the speed to generate messages. In most cases, the fault is caused when a large number of packets are generated in the network, and the CPU is too busy to handle received messages in time. Therefore, the message queue becomes full and the received subsequent data is discarded.


  1. Reduce the workload of the CPU by canceling some processes that are CPU-time consuming and unnecessary.
  2. If possible, wait till the CPU is idle and then configure relevant tasks.
  3. Collect log information and configuration information, and then contact technical support personnel.
Updated: 2019-05-29

Document ID: EDOC1000097294

Views: 96157

Downloads: 35

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Previous Next