JIRA

  • Log In Access more options
    • Online Help
    • GreenHopper Help
    • Agile Answers
    • Use Agile By Default
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Agile Access more options (Alt+g)
  • Create Issue
  • Mule
  • MULE-1409

Better support for ActiveMQ 4.x temp destinations

  • Agile Board
  • More Actions
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Improvement Improvement
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: Transport: JMS
  • Labels:
    None
  • User impact:
    Medium
  • Similar Issues:
    None

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

relates to

Task - A task that needs to be done. MULE-1080 Upgrade examples that Use ActiveMQ to version 4.1

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
  • Transitions
  • Commits
  • Source
  • Builds
Hide
Permalink
Andreas Guenther added a comment - 17/Sep/07 12:28 PM

Andrew,

Do you see any upcoming version in which we should tackle that issue? Maybe someone on your team can take care of it?

-Andreas

Show
Andreas Guenther added a comment - 17/Sep/07 12:28 PM Andrew, Do you see any upcoming version in which we should tackle that issue? Maybe someone on your team can take care of it? -Andreas
Hide
Permalink
Andrew Perepelytsya added a comment - 17/Sep/07 05:19 PM

This is required for sync request-response scenario. Additionally, it would fail only for topic replies. In reality synchronous replies from topic are very exotic, and so far I'm yet to see anyone reporting this particular problem. It can be implemented for completeness, however, I filed this issue so we don't forget it.

Show
Andrew Perepelytsya added a comment - 17/Sep/07 05:19 PM This is required for sync request-response scenario. Additionally, it would fail only for topic replies. In reality synchronous replies from topic are very exotic, and so far I'm yet to see anyone reporting this particular problem. It can be implemented for completeness, however, I filed this issue so we don't forget it.
Hide
Permalink
Ross Mason added a comment - 29/Nov/08 06:06 PM

Is this still required now that we can configure whether Tem destinations are to be used?

Show
Ross Mason added a comment - 29/Nov/08 06:06 PM Is this still required now that we can configure whether Tem destinations are to be used?

People

  • Assignee:
    Andrew Perepelytsya
    Reporter:
    Andrew Perepelytsya
Vote (0)
Watch (0)

Dates

  • Created:
    20/Feb/07 02:50 PM
    Updated:
    29/Nov/08 06:06 PM

Agile

  • View on Board
  • Atlassian JIRA (v5.0.7#734-sha1:8ad78a6)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.