All Products
Search
Document Center

ApsaraMQ for RocketMQ:Send and receive scheduled messages and delayed messages

Last Updated:Aug 18, 2023

This topic provides sample code on how to send and receive scheduled messages and delayed messages by using the HTTP client SDK for PHP.

Background information

  • Delayed messages are messages that are delivered by ApsaraMQ for RocketMQ brokers to consumers after a specific period of time.

  • Scheduled messages are messages that are delivered by ApsaraMQ for RocketMQ brokers to consumers at a specific point in time.

The code configurations of scheduled messages are the same as the code configurations of delayed messages over HTTP. Both types of messages are delivered to consumers after a specific period of time based on the attributes of messages.

For more information, see Scheduled messages and delayed messages.

Prerequisites

Before you start, make sure that the following operations are performed:

  • Install the SDK for PHP. For more information, see Prepare the environment.

  • Create the resources that you want to specify in the code in the ApsaraMQ for RocketMQ console. The resources include instances, topics, and consumer groups. For more information, see Create resources.

  • Obtain the AccessKey pair of your Alibaba Cloud account. For more information, see Create an AccessKey pair.

Send scheduled messages and delayed messages

The following sample code provides an example on how to send scheduled messages and delayed messages by using the HTTP client SDK for PHP:

<?php

require "vendor/autoload.php";

use MQ\Model\TopicMessage;
use MQ\MQClient;

class ProducerTest
{
    private $client;
    private $producer;

    public function __construct()
    {
        $this->client = new MQClient(
            // The HTTP endpoint. You can obtain the endpoint in the HTTP Endpoint section of the Instance Details page in the ApsaraMQ for RocketMQ console. 
            "${HTTP_ENDPOINT}",
            // Make sure that the environment variables ALIBABA_CLOUD_ACCESS_KEY_ID and ALIBABA_CLOUD_ACCESS_KEY_SECRET are configured. 
	          // The AccessKey ID that is used for authentication. 
	          getenv("ALIBABA_CLOUD_ACCESS_KEY_ID"),
	          // The AccessKey secret that is used for authentication. 
	          getenv('ALIBABA_CLOUD_ACCESS_KEY_SECRET')
        );

        // The topic in which the message is produced. You must create the topic in the ApsaraMQ for RocketMQ console. 
        $topic = "${TOPIC}";
        // The ID of the instance to which the topic belongs. You must create the instance in the ApsaraMQ for RocketMQ console. 
        // If the instance has a namespace, specify the ID of the instance. If the instance does not have a namespace, set the instanceID parameter to null or an empty string. You can obtain the namespace of the instance on the Instance Details page in the ApsaraMQ for RocketMQ console. 
        $instanceId = "${INSTANCE_ID}";

        $this->producer = $this->client->getProducer($instanceId, $topic);
    }

    public function run()
    {
        try
        {
            for ($i=1; $i<=4; $i++)
            {
                $publishMessage = new TopicMessage(
                    "hello mq! "// The message content. 
                );
                // The custom attributes of the message. 
                $publishMessage->putProperty("a", $i);
                // The message key. 
                $publishMessage->setMessageKey("MessageKey");
                // The period of time after which the broker delivers the message to the consumer. In this example, the broker delivers the message to the consumer 10 seconds later. Set this parameter to a timestamp in milliseconds. 
                // If you want to send a scheduled message, set the parameter to the time difference between the scheduled point in time and the current point in time. 
                $publishMessage->setStartDeliverTime(time() * 1000 + 10 * 1000);
                

                $result = $this->producer->publishMessage($publishMessage);

                print "Send mq message success. msgId is:" . $result->getMessageId() . ", bodyMD5 is:" . $result->getMessageBodyMD5() . "\n";
            }
        } catch (\Exception $e) {
            print_r($e->getMessage() . "\n");
        }
    }
}


$instance = new ProducerTest();
$instance->run();

?>

            

Subscribe to scheduled messages and delayed messages

The following sample code provides an example on how to consume scheduled messages and delayed messages by using the HTTP client SDK for PHP:

<?php

use MQ\MQClient;

require "vendor/autoload.php";

class ConsumerTest
{
    private $client;
    private $consumer;

    public function __construct()
    {
        $this->client = new MQClient(
            // The HTTP endpoint. To obtain the HTTP endpoint, log on to the Message Queue for Apache RocketMQ console. In the left-side navigation pane, click Instances. On the Instances page, click the name of your instance. On the Instance Details page, scroll to the Basic Information section and view the endpoint on the Endpoints tab. 
            "${HTTP_ENDPOINT}",
            // An AccessKey ID is used as the identifier for identity authentication. For information about how to obtain an AccessKey ID, see .
            "${ACCESS_KEY}",
            // An AccessKey secret is used as the password for identity authentication. For information about how to obtain an AccessKey secret, see .
            "${SECRET_KEY}"
        );

        // The topic to which the message you want to send belongs. The topic is created in the Message Queue for Apache RocketMQ console. 
        $topic = "${TOPIC}";
        // The ID of the group that you created in the Message Queue for Apache RocketMQ console. 
        $groupId = "${GROUP_ID}";
        // The ID of the instance to which the topic belongs. The instance is created in the Message Queue for Apache RocketMQ console. 
        // If the instance has a namespace, specify the ID of the instance. If the instance does not have a namespace, set the instance ID to null or an empty string. You can check whether your instance has a namespace on the Instances page in the Message Queue for Apache RocketMQ console. 
        $instanceId = "${INSTANCE_ID}";

        $this->consumer = $this->client->getConsumer($instanceId, $topic, $groupId);
    }

    public function ackMessages($receiptHandles)
    {
        try {
            $this->consumer->ackMessage($receiptHandles);
        } catch (\Exception $e) {
            if ($e instanceof MQ\Exception\AckMessageException) {
                // The broker may fail to receive a consumption acknowledgment (ACK) for a message from the consumer if the handle of the message times out. 
                printf("Ack Error, RequestId:%s\n", $e->getRequestId());
                foreach ($e->getAckMessageErrorItems() as $errorItem) {
                    printf("\tReceiptHandle:%s, ErrorCode:%s, ErrorMsg:%s\n", $errorItem->getReceiptHandle(), $errorItem->getErrorCode(), $errorItem->getErrorCode());
                }
            }
        }
    }

    public function run()
    {
        // Cyclically consume messages in the current thread. We recommend that you use multiple threads to concurrently consume messages. 
        while (True) {
            try {
                // Consume messages in long polling mode. 
                // If no message in the topic is available for consumption, the request is suspended on the broker for a period of time. This period of time is known as long polling period. If a message becomes available for consumption within this period of time, the broker immediately sends a response to the consumer. 
                $messages = $this->consumer->consumeMessage(
                    3, // The maximum number of messages that can be consumed at a time. In this example, the value is set to 3. The maximum value that you can specify is 16. 
                    3 // The length of a long polling period. Unit: seconds. In this example, the value is set to 3. The maximum value that you can specify is 30. 
                );
            } catch (\MQ\Exception\MessageResolveException $e) {
                // This exception is thrown when messages cannot be parsed due to invalid characters in the message body. 
                // The messages that can be parsed as expected. 
                $messages = $e->getPartialResult()->getMessages();
                // The messages that cannot be parsed as expected. 
                $failMessages = $e->getPartialResult()->getFailResolveMessages();

                $receiptHandles = array();
                foreach ($messages as $message) {
                    // The service logic for processing messages. 
                    $receiptHandles[] = $message->getReceiptHandle();
                    printf("MsgID %s\n", $message->getMessageId());
                }
                foreach ($failMessages as $failMessage) {
                    // Handle the message that cannot be parsed due to invalid characters in the message body. 
                    $receiptHandles[] = $failMessage->getReceiptHandle();
                    printf("Fail To Resolve Message. MsgID %s\n", $failMessage->getMessageId());
                }
                $this->ackMessages($receiptHandles);
                continue;
            } catch (\Exception $e) {
                if ($e instanceof MQ\Exception\MessageNotExistException) {
                    // No message is available for consumption, and the long polling mode continues to take effect. 
                    printf("No message, contine long polling!RequestId:%s\n", $e->getRequestId());
                    continue;
                }

                print_r($e->getMessage() . "\n");

                sleep(3);
                continue;
            }

            print "consume finish, messages:\n";

            // The service logic for processing messages. 
            $receiptHandles = array();
            foreach ($messages as $message) {
                $receiptHandles[] = $message->getReceiptHandle();
              
                printf("MessageID:%s TAG:%s BODY:%s \nPublishTime:%d, FirstConsumeTime:%d, \nConsumedTimes:%d, NextConsumeTime:%d,MessageKey:%s\n",
                    $message->getMessageId(), $message->getMessageTag(), $message->getMessageBody(),
                    $message->getPublishTime(), $message->getFirstConsumeTime(), $message->getConsumedTimes(), $message->getNextConsumeTime(),
                    $message->getMessageKey());
                print_r($message->getProperties());
            }

            // If the broker does not receive a consumption ACK for a message from the consumer before the period of time specified in $message->getNextConsumeTime() elapses, the message is consumed again. 
            // A unique timestamp is specified for the handle of a message each time the message is consumed. 
            print_r($receiptHandles);
            $this->ackMessages($receiptHandles);
            print "ack finish\n";
        }

    }
}

$instance = new ConsumerTest();
$instance->run();


?>