[
https://issues.apache.org/jira/browse/AMQ-7309?focusedWorklogId=628954&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-628954
]
ASF GitHub Bot logged work on AMQ-7309:
---------------------------------------
Author: ASF GitHub Bot
Created on: 28/Jul/21 09:36
Start Date: 28/Jul/21 09:36
Worklog Time Spent: 10m
Work Description: gemmellr edited a comment on pull request #682:
URL: https://github.com/apache/activemq/pull/682#issuecomment-888163344
> @gemmellr - Can you describe this scenario in more detail or a specific
use case? I want to make sure we are not breaking anything with throwing
unimplemented exceptions and how big of an edge case it is.
Take an ActiveMQ 5 JMS message object, and send that JMS Message somewhere
else using a different JMS client. E.g receive from a 5.x broker and publish
using the same message object to another type of broker...could be due to
communicating with different teams, companies, or handling a system transition,
etc.
As part of that process if the other provider is actually a JMS 2 client, it
will try to stamp the JMSDeliveryTime on the original message object like its
meant to. It may have handled the method not being implemented at all on JMS
1.x message objects since thats not so unexpected due to spec transition, but
will likely fail if the method actually exists but simply throws UOE as thats
unexpected.
Basically im saying at least implement the setter method and make 5.x call
it to set it to 0 during send (also handling the reverse case of sending other
messages through 5.x, ensuring they are properly stamped).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 628954)
Time Spent: 4.5h (was: 4h 20m)
> Add JMS 2.0 support
> -------------------
>
> Key: AMQ-7309
> URL: https://issues.apache.org/jira/browse/AMQ-7309
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, JMS client
> Reporter: Jean-Baptiste Onofré
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 5.17.0
>
> Time Spent: 4.5h
> Remaining Estimate: 0h
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
