[
https://issues.apache.org/jira/browse/AMQ-8398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17878366#comment-17878366
]
Aleksei Zotov commented on AMQ-8398:
------------------------------------
Thanks [~cshannon] !
I gave a round of testing to the fix in my local. It works fine!
{code:java}
./bin/activemq consumer --destination queue://test --messageCount 1
INFO: Loading '/Users/alekseizotov/opt/apache-activemq-5.18.5//bin/env'
INFO: Using java '/Users/alekseizotov/opt/jdk/current/Contents/Home/bin/java'
ACTIVEMQ_HOME: /Users/alekseizotov/opt/apache-activemq-5.18.5
ACTIVEMQ_BASE: /Users/alekseizotov/opt/apache-activemq-5.18.5
ACTIVEMQ_CONF: /Users/alekseizotov/opt/apache-activemq-5.18.5/conf
ACTIVEMQ_DATA: /Users/alekseizotov/opt/apache-activemq-5.18.5/data
INFO | Connecting to URL: failover://tcp://localhost:61616 as user: null
INFO | Consuming queue://test
INFO | Sleeping between receives 0 ms
INFO | Running 1 parallel threads
INFO | Successfully connected to tcp://localhost:61616
INFO | consumer-1 wait until 1 messages are consumed
INFO | consumer-1 Received 🙃🙂
INFO | consumer-1 Consumed: 1 messages
INFO | consumer-1 Consumer thread finished {code}
Â
Do you have any idea when we can expect 5.18.6 to be released?
Â
PS:
For those who might be interested to see details of the original brainstorming:Â
https://github.com/apache/activemq/pull/1284
> 4-byte Unicode message from JMS to STOMP will be corrupted
> ----------------------------------------------------------
>
> Key: AMQ-8398
> URL: https://issues.apache.org/jira/browse/AMQ-8398
> Project: ActiveMQ Classic
> Issue Type: Bug
> Components: Broker, STOMP, Transport
> Affects Versions: 5.16.3
> Reporter: Simon Lundstrom
> Assignee: Christopher L. Shannon
> Priority: Major
> Fix For: 6.2.0, 5.18.6, 6.1.4
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
> When sending a message from:
> JMS producer to STOMP consumer
> or
> 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:
> {code}
> Exception in thread "main" javax.jms.JMSException:
> java.io.UTFDataFormatException
> at
> org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:72)
> at
> org.apache.activemq.command.ActiveMQTextMessage.decodeContent(ActiveMQTextMessage.java:104)
> at
> org.apache.activemq.command.ActiveMQTextMessage.getText(ActiveMQTextMessage.java:84)
> at testkonsument.App.JMS(App.java:86)
> at testkonsument.App.main(App.java:42)
> Caused by: java.io.UTFDataFormatException
> at
> org.apache.activemq.util.MarshallingSupport.convertUTF8WithBuf(MarshallingSupport.java:389)
> at
> org.apache.activemq.util.MarshallingSupport.readUTF8(MarshallingSupport.java:358)
> at
> org.apache.activemq.command.ActiveMQTextMessage.decodeContent(ActiveMQTextMessage.java:101)
> ... 3 more
> {code}
> Using 4-byte unicode points
> from STOMP to STOMP
> or
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information, visit: https://activemq.apache.org/contact
