Uploaded image for project: 'Qpid JMS'
  1. Qpid JMS
  2. QPIDJMS-507

async send isn't really async

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical
    • Resolution: Invalid
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: qpid-jms-client
    • Labels:
      None

      Description

      When calling send with CompletionListener, the api indicates this create an async call.

      However, it seems that internally, there is still blocking.

      JmsSession has this code:

      transactionContext.send(connection, envelope, null)
      

      This in turn, calls:

      connection.send(envelope, new ProviderSynchronization() {
      

      And in there:

      try {
          provider.send(envelope, request);
          request.sync();
      } finally {
          requests.remove(request);
      }
      

      the sync call is blocking. so it seems there is no real async implementation?

      Also, the sync is called without timeout even if user sets a

      sendTimeout

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              yairogen yair ogen
            • Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: