amqp icon indicating copy to clipboard operation
amqp copied to clipboard

Go client for AMQP 0.9.1

Results 101 amqp issues
Sort by recently updated
recently updated
newest added

Hi, I've encountered an issue when trying to use AMQPLAIN authentication. It seems that the current implementation does not work out of the box. I looked for an official reference...

When producer push message and confirm message in one goroutine, deadlock would occur. In [confirms.go](https://github.com/streadway/amqp/blob/master/confirms.go), Publish method might wait lock infinitely that One method held once confirm channel blocked. So...

Hi, thanks for your great work on AMQP implementation! I having a problem on detect when channel enter in flow mode using RabbitMQ 3.8.15, after the channel creation i start...

There hasn't been any activity since last year . Is this project no longer maintained ? @streadway

I encountered a bug similar to this comment: https://github.com/streadway/amqp/issues/254#issuecomment-316401642 However, in a weak network environment, I get a deadlock after N+1 messages have been sent where N is the size...

"error":"bad_request","reason":"payload_not_string"} this is my test JSON { "properties": { "content_type": "application/json"}, "routing_key": "info", "payload_encoding": "string", "payload": { "records":{ "name":"testname"}}}

Relates to #266 and #464. The method adds the support of cancelling blocking operations in the Publish method. The PR replaces mutex with semaphore. The changes are not breaking. All...

- for example calls to `Publish` and `QueueDeclare` from multiple goroutines lead to messed up frames and eventual connection failure - i tested it by running 25 goroutines with infinite...

I tried to finish the work inside the #121 as best I could seeing the recommendation here https://github.com/streadway/amqp/issues/355#issuecomment-540677849 Here is the summary of my work * Made the changes requested...

**Problem:** Ambiguous behavior on Channel shutdown. If you consume using a Channel you cannot get the shutdown cause even if you use NotifyClose chan listener. Delivery chan could be selected...