Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-703

[jms] Enable call to onException in CompletionListener in async case for Artemis Core JMS

    XMLWordPrintable

Details

    • Story
    • Resolution: Done
    • Major
    • None
    • A-MQ 7.0.0.GA
    • None
    • Documentation (Ref Guide, User Guide, etc.), User Experience
    • Hide
      Cause:

      The onException method of the interface javax.jms.CompletionListener is not called when a non persistent message is failed to be delivered to a broker from a JMS message producer

      Consequence,

      This means that the client application is not notified and messages can be seen to disappear
       
      Fix,

      change the oNException method to be called when a non persitent message is not delivered because of an error

      Result
      The client application is notified when this happens
      Show
      Cause: The onException method of the interface javax.jms.CompletionListener is not called when a non persistent message is failed to be delivered to a broker from a JMS message producer Consequence, This means that the client application is not notified and messages can be seen to disappear   Fix, change the oNException method to be called when a non persitent message is not delivered because of an error Result The client application is notified when this happens

    Description

      We are struggling to configure/code up an Artemis Core JMS 2.0 async producer with a completion listener so that when exception occurs, onException method is invoked. When we run a client and do actions like, sending to an address we're un-authorised queue or when send and broker is down, we would expect to have onException invoked, to know the message send fails, however in the async case this does not occur.

      Attachments

        Issue Links

          relates to

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-945 Non-persistent messages lost in non-failure scenarios when authorization fails, because delivery mode defaults to asynchronous

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. ENTMQBR-947 Check authorization when message producer is set up

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Task - Represents a small unit of work that is not end-user facing. ENTMQBR-2368 Add documentation for JMS 2.0 Completion Listener

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • New
          cloned to

          ARTEMIS-1545 Loading...

          Activity

            People

              rh-ee-ataylor Andy Taylor
              rhn-support-rkieley Roderick Kieley
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: