Mule
  1. Mule
  2. MULE-1409

Better support for ActiveMQ 4.x temp destinations

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix or Usage Issue
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Transport: JMS
    • Labels:
      None
    • User impact:
      Medium
    • Similar Issues:
      MULE-4060Bump ActiveMQ version to 4.1.2
      MULE-997Better support for JMS 1.0.2b
      MULE-1931Temp JMS destinations should reference a connector
      MULE-1554LoanBroker ESB sample temp destination consumer error on shutdown
      MULE-769Properly dispose of JMS temporary destinations
      MULE-3100Better Header expression support
      MULE-91Support for Jndi Jms destinations
      MULE-6239Better Xpath support
      MULE-9348Merge 3.x to 4.x
      MULE-4617JMSReplyToHandler tries to send to JMS endpoint synchronously (creating temp destination) rather than dispatching

      Description

      AMQ 4.x has specific prefixes for the destination names:

      queue://
      topic://
      temp-queue://
      temp-topic://

      JmsMessageDispatcher might need to be replaced with a ActiveMQ4-specific dispatcher to handle temporary topic replis, at the moment it works by accident only (see JmsMessageDispatcher around line 160).

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Andrew Perepelytsya
              Reporter:
              Andrew Perepelytsya
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development