When sending a message from:
JMS producer to STOMP consumer
STOMP producer to JMS consumer
which contains a 4-byte unicode code points e.g. https://unicode-table.com/en/1F5A4/ there is a corruption of the message.
In the JMS to STOMP case the code point gets converted to:
ef bf bd ef bf bd when it should be f0 9f 96 a4.
and in the STOMP to JMS case the JMS client throws an exception:
Using 4-byte unicode points
from STOMP to STOMP
from JMS to JMS
is not a problem, both works and does not corrupt the code point.
Note that 2- (e.g. https://unicode-table.com/en/00F6/) or 3-byte (e.g. https://unicode-table.com/en/2614/) Unicode code points does NOT get corrupted, even if the same message includes a 4-byte Unicode code point.