[GH-ISSUE #278] [BUG] Enqueue message from NodeJS #109

Closed
opened 2026-03-02 05:18:45 +03:00 by kerem · 2 comments
Owner

Originally created by @acgfbr on GitHub (Jun 8, 2021).
Original GitHub issue: https://github.com/hibiken/asynq/issues/278

Originally assigned to: @hibiken on GitHub.

Describe the bug
My system enqueue all of messages in nodejs, just route to micro service enqueuer, example:
i have multi queue system in sqs, php and im trying to rollout all of this systems to go, but i want to enqueue in node to sqs and golang

I'm queuing a payload from nodejs and asynq can't remove the message

To Reproduce
Steps to reproduce the behavior (Code snippets if applicable):

NodeJS code
image

Payload in redis by NodeJS
Payload in redis by Golang asynq enqueue

image

The golang message enqueued by go proccess normally, nodejs message not removed from queue
image

Message stuck:
image

The payload as 100% matching, what can i be doing wrong?
Can u help me ?

My go code from server:
image

Job:
image

Originally created by @acgfbr on GitHub (Jun 8, 2021). Original GitHub issue: https://github.com/hibiken/asynq/issues/278 Originally assigned to: @hibiken on GitHub. **Describe the bug** My system enqueue all of messages in nodejs, just route to micro service enqueuer, example: i have multi queue system in sqs, php and im trying to rollout all of this systems to go, but i want to enqueue in node to sqs and golang I'm queuing a payload from nodejs and asynq can't remove the message **To Reproduce** Steps to reproduce the behavior (Code snippets if applicable): NodeJS code ![image](https://user-images.githubusercontent.com/8755427/121115061-04ff1500-c7eb-11eb-9806-9785993950d9.png) Payload in redis by NodeJS Payload in redis by Golang asynq enqueue ![image](https://user-images.githubusercontent.com/8755427/121115142-2bbd4b80-c7eb-11eb-863c-49f5a4f9d27b.png) The golang message enqueued by go proccess normally, nodejs message not removed from queue ![image](https://user-images.githubusercontent.com/8755427/121115183-38da3a80-c7eb-11eb-90ce-a7ff994b29d1.png) Message stuck: ![image](https://user-images.githubusercontent.com/8755427/121115454-79d24f00-c7eb-11eb-8e9b-fecc71da7a8b.png) The payload as 100% matching, what can i be doing wrong? Can u help me ? My go code from server: ![image](https://user-images.githubusercontent.com/8755427/121115831-f8c78780-c7eb-11eb-8a29-8c091f3e2683.png) Job: ![image](https://user-images.githubusercontent.com/8755427/121115848-00872c00-c7ec-11eb-8a0f-950a16b91296.png)
kerem 2026-03-02 05:18:45 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@crossworth commented on GitHub (Jun 8, 2021):

Hi, maybe this is related to this: https://github.com/hibiken/asynq/issues/109#issuecomment-796809596

Which should be fixed when the API uses a byte slice as payload (https://github.com/hibiken/asynq/pull/253).

<!-- gh-comment-id:856401460 --> @crossworth commented on GitHub (Jun 8, 2021): Hi, maybe this is related to this: https://github.com/hibiken/asynq/issues/109#issuecomment-796809596 Which should be fixed when the API uses a byte slice as payload (https://github.com/hibiken/asynq/pull/253).
Author
Owner

@acgfbr commented on GitHub (Jun 8, 2021):

Oh great, i change the order of json and now working, thanks man!
image

<!-- gh-comment-id:856405068 --> @acgfbr commented on GitHub (Jun 8, 2021): Oh great, i change the order of json and now working, thanks man! ![image](https://user-images.githubusercontent.com/8755427/121117387-6eccee00-c7ee-11eb-8eec-7c775d0130c7.png)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/asynq#109
No description provided.