message-queue

问题 I am trying to start RabbitMQ service on my local Windows laptop but I keep getting this error: I first downloaded erlang (OTP 19.0 Windows 64-bit Binary File) from here: http://www.erlang.org/downloads. Then I downloaded RabbitMQ from here: https://www.rabbitmq.com/install-windows.html Erlang seems to have installed correctly - I don't see any errors in the logs. RabbitMQ shows this message in the installation logs: Installing RabbitMQ service... The filename, directory name, or volume label

问题 Is there any way to implement request-response pattern with mosca MQTT to "check reply from the client and re publish if i dont receive expected reply within expected time". I believe this is possible in Mqtt 5, but as of now, I have to use Mosca broker with QoS 1(which support until Mqtt 3.1.1) I am looking for a Node js workaround to achieve this. 回答1: As per my comment you can implement a request-response pattern with any MQTT broker but, prior to v5, you need to implement this yourself

问题 Is there any way to implement request-response pattern with mosca MQTT to "check reply from the client and re publish if i dont receive expected reply within expected time". I believe this is possible in Mqtt 5, but as of now, I have to use Mosca broker with QoS 1(which support until Mqtt 3.1.1) I am looking for a Node js workaround to achieve this. 回答1: As per my comment you can implement a request-response pattern with any MQTT broker but, prior to v5, you need to implement this yourself

问题 I can not find how to work properly with mq_timedreceive, can anyone give me an example? ssize_t mq_timedreceive(mqd_t mqdes, char *msg_ptr, size_t msg_len, unsigned *msg_prio, const struct timespec *abs_timeout); I want timereceive to do not spent more than 20 seconds waiting. Thank you very much. 回答1: struct timespec tm; clock_gettime(CLOCK_REALTIME, &tm); tm.tv_sec += 20; // Set for 20 seconds if( 0 > mq_timedreceive( fd, buf, 4096, NULL, &tm ) ) { ... } Take a look at the full description

问题 I can not find how to work properly with mq_timedreceive, can anyone give me an example? ssize_t mq_timedreceive(mqd_t mqdes, char *msg_ptr, size_t msg_len, unsigned *msg_prio, const struct timespec *abs_timeout); I want timereceive to do not spent more than 20 seconds waiting. Thank you very much. 回答1: struct timespec tm; clock_gettime(CLOCK_REALTIME, &tm); tm.tv_sec += 20; // Set for 20 seconds if( 0 > mq_timedreceive( fd, buf, 4096, NULL, &tm ) ) { ... } Take a look at the full description

问题 I can not find how to work properly with mq_timedreceive, can anyone give me an example? ssize_t mq_timedreceive(mqd_t mqdes, char *msg_ptr, size_t msg_len, unsigned *msg_prio, const struct timespec *abs_timeout); I want timereceive to do not spent more than 20 seconds waiting. Thank you very much. 回答1: struct timespec tm; clock_gettime(CLOCK_REALTIME, &tm); tm.tv_sec += 20; // Set for 20 seconds if( 0 > mq_timedreceive( fd, buf, 4096, NULL, &tm ) ) { ... } Take a look at the full description

问题 I am using Cake 3.x I need to have the following things set up. A job queue to queue jobs that require long processing in the background A feed (like Facebook Feed) that informs various users of what's happening within the app This is what I have in terms of requirements: Job Queue This needs to be persistent and reliable. Meaning to say if the server suddenly rebooted, any jobs queued but not yet executed will still be there waiting to be processed upon reboot. News Feed / Activity Stream

问题 I am using Cake 3.x I need to have the following things set up. A job queue to queue jobs that require long processing in the background A feed (like Facebook Feed) that informs various users of what's happening within the app This is what I have in terms of requirements: Job Queue This needs to be persistent and reliable. Meaning to say if the server suddenly rebooted, any jobs queued but not yet executed will still be there waiting to be processed upon reboot. News Feed / Activity Stream

问题 I was working with Dead letter Queue in Amazon SQS. I want that whenever a new message is received by the queue it should raise a CloudWatch alarm. The problem is I configured an alarm on the metric: number_of_messages_sent of the queue but this metric don't work as expected in case of Dead letter Queues as mentioned in the Amazon SQS Dead-Letter Queues - Amazon Simple Queue Service documentation. Now some suggestions on this were use number_of_messages_visible but I am not sure how to

问题 So I have an azure function acting as a queue trigger that calls an internally hosted API. There doesn't seem to be a definitive answer online on how to handle a message that could not be processed due to issues other than being poisonous. An example: My message is received and the function attempts to call the API. The message payload is correct and could be handled however the API/service is down for whatever reason (this time will likely be upwards of 10 minutes). Currently what happens is