[ 
https://issues.apache.org/jira/browse/AMQ-8324?focusedWorklogId=947696&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-947696
 ]

ASF GitHub Bot logged work on AMQ-8324:
---------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Dec/24 01:02
            Start Date: 11/Dec/24 01:02
    Worklog Time Spent: 10m 
      Work Description: kenliao94 commented on PR #1364:
URL: https://github.com/apache/activemq/pull/1364#issuecomment-2533379072

   Thanks for the feedback @cshannon, @tabish121 and @mattrpav . So I didn't 
exactly copied and pasted the AsyncCallback code, I did a few manual testing to 
make sure the ordering is honor. I will see how I can test it more 
comprehensively in the unit test. One challenge I had with unit testing is it 
doesn't simulate delayed in Ack. I built a hacked broker to simulate ack 
delayed for certain messages (if the message content contains a secret command) 
and it did honor the ordering. I will make sure I add more testcases and 
present it here.
   
   Like I described in the commit description, the broker will not send out 
acknowledge of the send request out of order. It can dispatch to the consumer 
in different order due to message priority, but for same destination, the order 
is honored. Hence I didn't implement the logic of making sure the order is 
honored on the client side. If we feel that we need to enforce it on the client 
side then I can see what I can do on the client code.
   
   Regarding session close: yes 100%. That's why I would love feedback on that 
on what testcases I miss. Especially I needed to add a concurrent data 
structure to block until all async sends have completed. That one I can add 
unit tests coverage more easily.
    




Issue Time Tracking
-------------------

    Worklog Id:     (was: 947696)
    Time Spent: 2h  (was: 1h 50m)

> Implement JMS 2.0 MessageProducer CompletionListener methods
> ------------------------------------------------------------
>
>                 Key: AMQ-8324
>                 URL: https://issues.apache.org/jira/browse/AMQ-8324
>             Project: ActiveMQ Classic
>          Issue Type: New Feature
>            Reporter: Matt Pavlovich
>            Assignee: Matt Pavlovich
>            Priority: Major
>              Labels: #jms2
>             Fix For: 6.2.0
>
>          Time Spent: 2h
>  Remaining Estimate: 0h
>
> CompletionListener, etc



--
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


Reply via email to