Error message | Programming language | Cause | Solution |
TimeoutException
| Java |
Note This error is reported only in Internet-facing ApsaraMQ for Kafka instances. | Make sure that the server is correctly configured. Run the telnet command to check the network connection. If the network connection is normal, check whether the authentication is successful. For more information, see the following references:
Note You can apply this solution to Internet-facing ApsaraMQ for Kafka instances.
|
run out of brokers
| Go |
Authentication failed for user
| Python |
Leader is not available
| All | This error is temporarily reported when a topic is initialized. If the error persists, the topic may not exist. | Log on to the ApsaraMQ for Kafka console. Check whether the topic exists. If the topic does not exist, create a topic. For information about how to create a topic, see Step 3: Create resources.
|
leader is in election
|
array index out of bound exception
| Java | Spring Cloud uses a built-in format to parse messages. | The following solutions are provided: We recommend that you use Spring Cloud Stream to send and consume messages. If you use another method to send messages but use Spring Cloud Stream to consume messages, set the headerMode parameter to raw to disable message parsing. For example, you call a native Java client to send messages but use Spring Cloud Stream to consume messages. For more information, see Spring Cloud Stream Reference Guide.
|
No such configuration property: "sasl.mechanisms"
| | The Simple Authentication and Security Layer (SASL) and Secure Sockets Layer (SSL) modules are not installed or are not properly installed. | Run the following commands to install the SASL and SSL modules:
Note In this example, the CentOS system is used. For other OSs, see the official websites or use a third-party search engine to search for related information. |
No worthy mechs found
|
No KafkaClient Entry
| Java | The kafka_client_jaas.conf configuration file is not found. | Prepare the kafka_client_jaas.conf file and save the file in a directory, such as /home/admin. The logon security settings of a Java client are configured in the system. You can use one of the following methods to configure the settings: For more information, see JAAS Login Configuration File. |
Error sending fetch request
| Java | Messages fail to be pulled by the consumer. Possible causes: Network issues Message pulling timeout
| Make sure that the server is correctly configured. Run the telnet command to check the network connection. If the network connection is normal, message pulling may time out. You can modify the following parameters to limit the number of messages that can be pulled each time. fetch.max.bytes: the maximum number of bytes that are returned by the broker from a single pull. max.partition.fetch.bytes: the maximum number of bytes that are returned by one partition on the broker from a single pull.
In the ApsaraMQ for Kafka console, you can view the traffic limit on the broker in the Basic Information section of the Instance Details page. If the instance is a virtual private cloud (VPC)-connected instance, view the value of the Traffic Specification parameter. If the instance is an Internet-connected instance, view the value of the Public Traffic parameter.
|
DisconnectException
|
CORRUPT_MESSAGE
| All | Cloud storage: If your client version is 3.0 or later, the idempotence feature is automatically enabled. However, the idempotence feature is not supported by cloud storage. Local storage: The message key is not specified when you run the log compaction command.
| |