RabbitMQ/Krakend/NestJS：异步代理消费消息后POST接口无请求体问题

KrakenD已经成功消费MQ消息，但把消息POST到service-c的/greeted接口时，打印的请求体是空对象{}。相关配置和代码如下：

KrakenD配置（krakend.json） #

"async_agent": [
    {
      "name": "test-agent",
      "connection": {
        "max_retries": 10,
        "backoff_strategy": "exponential-jitter"
      },
      "consumer": {
        "topic": "krakend",
        "workers": 5
      },
      "backend": [
        {
          "url_pattern": "/greeted",
          "method": "POST",
          "host": [ "http://127.0.0.1:2999" ],
          "disable_host_sanitize": false
        }
      ],
      "extra_config": {
        "async/amqp": {
          "host": "amqp://guest:guest@localhost:5672/",
          "name": "krakend",
          "exchange": "ApiGatewayExchange",
          "durable": true,
          "delete": false,
          "exclusive": false,
          "no_wait": false,
          "auto_ack": false
        }
      }
    }
  ]

Service-A发送消息代码 #

export class AppService {
  constructor(@Inject('GREETING_SERVICE') private client: ClientProxy){}

  getHello(): ResponseDTO {
    const responseDTO: ResponseDTO = {
      action: 'Hello',
      service: 'from service A'
    }
    this.client.emit('', responseDTO);
    return responseDTO;
  }
}

Service-A的MQ客户端配置 #

imports: [
    ClientsModule.register([
      {
        "name": "GREETING_SERVICE",
        transport: Transport.RMQ,
        options: {
          urls: ['amqp://test:test@localhost:5672/'],
          queue: 'krakend'
        }
      }
    ])
  ],

Service-C接收接口代码 #

@Post('greeted')
  TestHello(@Body() data: any) {
    console.log(data)
    return data
  }

1. KrakenD未配置消息到请求体的映射 #

KrakenD默认不会自动将消费到的MQ消息作为POST请求体发送，必须在backend的extra_config中显式配置backend/http，指定消息内容的去向：

修改KrakenD的backend部分：

"backend": [
  {
    "url_pattern": "/greeted",
    "method": "POST",
    "host": [ "http://127.0.0.1:2999" ],
    "disable_host_sanitize": false,
    "extra_config": {
      "backend/http": {
        "body": "${body}"
      }
    }
  }
]

${body}表示直接将消费到的原始消息内容作为POST请求体发送。

2. NestJS发送的消息被封装 #

NestJS的ClientProxy.emit()方法会自动把你的responseDTO封装成包含pattern和data字段的结构（比如{ pattern: '', data: { action: 'Hello', ... } }）。KrakenD拿到的是这个封装后的对象，若直接用${body}，service-c收到的是整个封装结构，接口没对应解析就会返回空。

修复方式二选一：

• 方式一：在KrakenD中提取真实数据
  如果消息结构是{ data: ... }，将backend的body配置改为${body.data}：

"extra_config": {
  "backend/http": {
    "body": "${body.data}"
  }
}

同时给async/amqp添加解析配置，确保正确反序列化：

"extra_config": {
  "async/amqp": {
    // 原有配置保留
    "consumer": {
      "raw": false,
      "unmarshal": true
    }
  }
}

• 方式二：让NestJS直接发送原始JSON
  绕过NestJS的封装，用底层AMQP客户端发送原始消息：

import { RabbitMQClient } from '@nestjs/microservices/client/rabbitmq-client';

// 在AppService中注入RabbitMQClient
constructor(@Inject('GREETING_SERVICE') private client: ClientProxy, private rmqClient: RabbitMQClient) {}

getHello(): ResponseDTO {
  const responseDTO: ResponseDTO = {
    action: 'Hello',
    service: 'from service A'
  };
  // 直接将JSON转为Buffer发送到队列
  this.rmqClient.getChannelRef().sendToQueue('krakend', Buffer.from(JSON.stringify(responseDTO)));
  return responseDTO;
}

3. 检查MQ账号权限一致性 #

Service-A用的MQ账号是test:test，KrakenD用的是guest:guest，需确保两个账号都有权限访问krakend队列和ApiGatewayExchange交换器，避免消息被拦截。

4. 确认Service-C的JSON解析正常 #

确保Service-C的NestJS应用开启了JSON请求体解析（默认开启，若修改过中间件需检查）：

// main.ts中确认存在该配置
app.use(bodyParser.json());

内容的提问来源于stack exchange，提问作者heneftees