Uploaded image for project: 'HornetQ'
  1. HornetQ
  2. HORNETQ-1242

forward compatibility is broken

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 2.4.1.Final
    • Component/s: Core, JMS
    • Labels:
      None
    • Environment:

      JBoss EAP 6.x

      Description

      At the moment HornetQ only guarantees that older client should be able to connect to newer message broker but not the other way around. This is causing a lot of problems for customers who are migrating from EAP 5 to EAP 6 and would like to be able to run both versions of the product to run side by side and be able to send/consume messages between different versions.

      HornetQ internal protocol should be able to step up/step down depending on which version of broker the client is connecting to.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                jbertram Justin Bertram
                Reporter:
                raggz Tom Ross
              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: