-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error from version 2.4.8 #595
Comments
Is it possible to capture Frame level logs and share it here? If you use SASL PLAIN authentication, please remove the SASL frames. |
[11:22:30.060] SEND AMQP 0 1.0.0
[11:22:59.224] SEND (ch=0) detach(handle:0,closed:True) I also checked, what is AmpqException: Operation 'Accept' is invalid, under state DetachSent. |
For example same with version 2.4.0 (I'm not sure from which version problem appears. I wrote before that version 2.4.7 is ok, but no, last version which works for me 2.4.6. ) [11:47:33.203] SEND AMQP 0 1.0.0 |
From the log it was an issue with the broker. It did not respond to the client's session/link initiation commands. |
platform:Solace PubSub+ 3560,version:10.4.1.189 At the moment I use Amqpnetlite 2.4.6 version and it is working ok. |
The working version # 2.4.6 helped. I believe it was a regression in 2.4.7. In your code there should be a blocking call after the for loop (probably waiting for exit signal from console?). As a workaround, you can add a Task.Yield() call after connection creation. We will fix the bug soon.
|
Yes, Task.Yield() helps. And yes - I use Console.ReadKey. |
Dotnet 9
nuget packege Amqpnetlite.Core
From version 2.4.8 (2.4.9, 2.4.10, 2.4.11) I have problems. 2.4.7 and earlier works fine.
I use this code:
As you can see, nothing special. Sometimes I get some messages, but when I close receiverlink await link.CloseAsync(), I suddenly receive bunch of messages, which I should received earlier. Looks like that messages is stuck somewhere.
About broker, I can't say nothing specific - it is third party, and they states that it supports AMQP 1.0.
The text was updated successfully, but these errors were encountered: