A-MQ 6: STOMP destination format

Solution Verified - Updated -

Issue

The STOMP protocol does not mandate any particular interpretation of the destination: header (e.g., in a SUBSCRIBE frame). The interpretation of the destination is stated to be vendor-specific. How does A-MQ 6.x interpret this header?

Environment

  • Red Hat JBoss A-MQ
    • 6.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.