Skip to content
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

Unexpected connection close when publishing multiple messages #21

Closed
pardahlman opened this issue Jan 22, 2016 · 0 comments
Closed

Unexpected connection close when publishing multiple messages #21

pardahlman opened this issue Jan 22, 2016 · 0 comments
Assignees
Labels
Milestone

Comments

@pardahlman
Copy link
Owner

When publishing a lot of messages (1'000'000+) there are some flip sides, like

RabbitMQ.Client.Exceptions.OperationInterruptedException: The AMQP operation was interrupted: AMQP close-reason, initiated by Peer, code=504, text="CHANNEL_ERROR - expected 'channel.open'", classId=60, methodId=40, cause=
   at RabbitMQ.Client.Impl.SimpleBlockingRpcContinuation.GetReply(TimeSpan timeout)
   at RabbitMQ.Client.Impl.ModelBase.ModelRpc(MethodBase method, ContentHeaderBase header, Byte[] body)
   at RabbitMQ.Client.Framing.Impl.Model._Private_ChannelOpen(String outOfBand)
   at RabbitMQ.Client.Framing.Impl.AutorecoveringConnection.CreateNonRecoveringModel()
   at RabbitMQ.Client.Framing.Impl.AutorecoveringConnection.CreateModel()
   at RawRabbit.Common.ChannelFactory.<>c.<CreateChannelAsync>b__12_0(Task`1 c)

This should be fixed

@pardahlman pardahlman self-assigned this Jan 22, 2016
@pardahlman pardahlman added this to the 1.8.2 milestone Jan 22, 2016
pardahlman pushed a commit that referenced this issue Jan 23, 2016
Prevent channel shutdown if still active
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant