[
https://issues.apache.org/jira/browse/ARTEMIS-4657?focusedWorklogId=908587&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-908587
]
ASF GitHub Bot logged work on ARTEMIS-4657:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Mar/24 15:31
Start Date: 06/Mar/24 15:31
Worklog Time Spent: 10m
Work Description: tabish121 commented on code in PR #4833:
URL: https://github.com/apache/activemq-artemis/pull/4833#discussion_r1514692706
##########
artemis-protocols/artemis-openwire-protocol/src/main/java/org/apache/activemq/artemis/core/protocol/openwire/OpenWireMessageConverter.java:
##########
@@ -590,9 +590,9 @@ private static ActiveMQMessage
toAMQMessage(MessageReference reference,
}
amqMsg.setCommandId(commandId);
- final SimpleString corrId = getObjectProperty(coreMessage,
SimpleString.class, OpenWireConstants.JMS_CORRELATION_ID_PROPERTY);
- if (corrId != null) {
- amqMsg.setCorrelationId(corrId.toString());
+ final Object correlationID = coreMessage.getCorrelationID();
Review Comment:
It seems like we could retain support for carried byte[] type correlation
IDs by decoding a UTF8 string here as the receiving Openwire client would
either decode it if the getter for bytes was called or would just return a
string value from the non-bytes getter, which allows basic interop. Equally
there are types that could be carried in an AMQP message correlation ID like a
UUID that could make sense to convert to string as well as it could allow some
edge case interop for receivers wanting to sync up correlation ID values. It
might make sense to have some consideration for those cases and what we should
or shouldn't be allowing to propagate to an Openwire client.
Issue Time Tracking
-------------------
Worklog Id: (was: 908587)
Time Spent: 2.5h (was: 2h 20m)
> Support correlation ID compatibility between JMS clients
> --------------------------------------------------------
>
> Key: ARTEMIS-4657
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4657
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Justin Bertram
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Currently there are some use-cases with both {{String}} and {{byte[]}} values
> of JMS correlation ID that don't work between Core, OpenWire, and AMQP. We
> should support as many as possible.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
