[Need Help] Why I got "PooledUnsafeDirectByteBuf" when connecting with websocket

Gatling (Open-Source)
1

Dear there,

Gatling: “3.0.3”
Scala: 2.12.8

My gatling logs below, could you please tell me why there are messages:

  • Read msg=TextWebSocketFrame(data: PooledUnsafeDirectByteBuf(ridx: 0, widx: 85, cap: 85))\
  • ctx.write msg=TextWebSocketFrame(data: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 32, cap: 96))

Logs:

12:31:35.712 [GatlingSystem-akka.actor.default-dispatcher-5] DEBUG i.gatling.http.action.ws.fsm.WsActor - Connected, no checks, performing onConnected action before performing next action
12:31:35.713 [gatling-http-1-2] DEBUG i.g.h.client.impl.WebSocketHandler - Read msg=TextWebSocketFrame(data: PooledUnsafeDirectByteBuf(ridx: 0, widx: 85, cap: 85))
12:31:35.716 [GatlingSystem-akka.actor.default-dispatcher-5] INFO i.g.http.action.ws.WsSendTextFrame - Sending text frame 42/chat,[“subscribe”, “default”] with websocket ‘gatling.http.webSocket’: Scenario ‘Testing OpenPaaS chat send a message’, UserId #1
12:31:35.716 [gatling-http-1-2] DEBUG i.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame opCode=1
12:31:35.716 [gatling-http-1-2] DEBUG i.n.h.c.h.w.WebSocket08FrameDecoder - Decoding WebSocket Frame length=2
12:31:35.717 [gatling-http-1-2] DEBUG i.g.h.client.impl.WebSocketHandler - Read msg=TextWebSocketFrame(data: PooledUnsafeDirectByteBuf(ridx: 0, widx: 2, cap: 2))
12:31:35.720 [GatlingSystem-akka.actor.default-dispatcher-5] DEBUG i.gatling.http.action.ws.fsm.WsActor - Send text frame Send message 42/chat,[“subscribe”, “default”]
12:31:35.722 [GatlingSystem-akka.actor.default-dispatcher-5] DEBUG i.gatling.http.action.ws.fsm.WsActor - Trigger check after sending text frame
12:31:35.722 [gatling-http-1-2] DEBUG i.g.h.client.impl.WebSocketHandler - ctx.write msg=TextWebSocketFrame(data: UnpooledByteBufAllocator$InstrumentedUnpooledUnsafeHeapByteBuf(ridx: 0, widx: 32, cap: 96))

Thanks in advanced!

2

2 things:

  1. you’re using the outdated 3.0.3 version, current version is 3.3.1
  2. you’re either forcing DEBUG logging level on Netty’s package, or failing to properly configure logback, hence the verbose logs