Skip to content

Instantly share code, notes, and snippets.

@lukebakken

lukebakken/stackoverflow-75574227.md

Last active March 2, 2023 18:27
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lukebakken/621e19cdd117599011c0e905ece59650 to your computer and use it in GitHub Desktop.
Save lukebakken/621e19cdd117599011c0e905ece59650 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
stackoverflow-75574227.md

Hello -

Thanks for using RabbitMQ. I'm a member of the core engineering team.

Carefully look at the first 16 octets in this error log message:

2023-02-26 16:43:12.635470+00:00 [error] <0.1056.0>  operation none caused a connection exception frame_error: "type 3, first 16 octets = <<\"{\\\"payload\\\":{\\\"res\">>: {invalid_frame_end_marker,\n                                                      
99}"
2023-02-26 16:43:15.638860+00:00 [error] <0.1056.0> closing AMQP connection <0.1056.0> (10.244.0.18:60608 -> 10.244.0.21:5672):
2023-02-26 16:43:15.638860+00:00 [error] <0.1056.0> fatal_frame_error

It looks as though your client application tried to publish a message containing a RabbitMQ error log message (invalid_frame_end_marker) BACK to RabbitMQ and then another error happened.

What you should do at this point is share a git repository containing a complete, runnable set of code that I can use to reproduce this issue. Basically I should just clone the repo, and execute a command. Assume there is a 3-node RabbitMQ cluster available, or, provide your complete minikube configuration.

Thanks - Luke

@lukebakken
Copy link
Author

Let's continue discussion here - https://github.com/andrinheusser/rabbitmq-frame-errors-debug/issues/1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment