UNEXPECTED_FRAME - expected content header for class 60, got non content header frame instead

[oceanho]

hi, I am use client: amqplib 0.7.1 , https://www.npmjs.com/package/amqplib rabbitmq-server: 3.7 It's will got the fllowing error on my client

UNEXPECTED_FRAME - expected content header for class 60, got non content header frame instead

any idea, thanks.

This is my docker-compose yaml file of mq deploy.

version: "3.7"
services:
  mq-n1:
    image: rabbitmq:3.7-management
    hostname: rabbit-c1
    network_mode: host
    restart: always
    environment:
      - RABBITMQ_ERLANG_COOKIE=rabbit-cookie
      - RABBITMQ_DEFAULT_USER=private
      - RABBITMQ_DEFAULT_PASS=private
  mq-proxy:
    image: cloudamqp/amqproxy
    network_mode: host
    restart: always
    command: amqp://127.0.0.1:5672 --port=55672

[carlhoerberg]

Why do you use a proxy when you have 0 latency and a client that can hold long lived connections?

On Sun, 7 Nov 2021, 14:27 Ocean Ho, @.***> wrote:

hi, I am use client: amqplib 0.7.1 , https://www.npmjs.com/package/amqplib rabbitmq-server: 3.7 It's will got the fllowing error on my client

UNEXPECTED_FRAME - expected content header for class 60, got non content header frame instead

any idea, thanks.

This is my docker-compose yaml file of mq deploy.

version: "3.7"services: mq-n1: image: rabbitmq:3.7-management hostname: rabbit-c1 network_mode: host restart: always environment:

• RABBITMQ_ERLANG_COOKIE=rabbit-cookie
• RABBITMQ_DEFAULT_USER=private
• RABBITMQ_DEFAULT_PASS=private mq-proxy: image: cloudamqp/amqproxy network_mode: host restart: always command: amqp://127.0.0.1:5672 --port=55672

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cloudamqp/amqproxy/issues/59, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABL6TVGF4WFI62XNE7STDDUKZ5FXANCNFSM5HQ2I6ZQ .

[oceanho]

Our rabbitmq memory has been growing and not releasing, so I did some tests with it, hoping to solve this problem, and then encountered this error

[oceanho]

We used some tools and commands provided by mq. What we saw is that the memory of binary and connection_other has been growing. Through the management web of mq, we can see that after a long period of time, connections and channels will become a lot, but even in business During low peak periods, they will not decrease, and only restart mq to return to normal. I don't know why this happens.

[oceanho]

@carlhoerberg Thank for quickly answer, I know that we mq memory problem that has nothing to do with amqproxy.

[oceanho]

But I am more curious why amqproxy has Unexceped Frame problem

[carlhoerberg]

Yes, me too, but without a reproducible test case it's very hard to know what it can be.