Stomp Broker Relay may ignore configured destination prefixes [SPR-16265]

[spring-projects-issues]

Rémi Alvergnat opened SPR-16265 and commented

There's a bug in StompHeaderAccessor class, method updateStompCommandAsClientMessage.

Problem occurs when getCommand() returns null. setHeader is called with SEND command, but command variable is not set after that and method returns null instead of SEND

It cause the stomp broker relay to ignore destination prefixes because command is null (see StompBrokerRelayMessageHandler L507).

---

Affects: 4.3.13, 5.0.2

Reference URL: #1616

Issue Links:

• Reduce access on headers for STOMP messaging [SPR-16165] #20713 Reduce access on headers for STOMP messaging

Referenced from: commits 4fe94df, 76dcde9

Backported to: 4.3.14

[spring-projects-issues]

Rossen Stoyanchev commented

PR #1616

[spring-projects-issues]

Rossen Stoyanchev commented

It looks like this was introduced recently with the changes for #20713.

[spring-projects-issues]

Christoph Dreis commented

Just saw this. Good catch. As I did #20713 originally, I worried that I might have broken it from the start, but it seems to have only sneaked into the backport.