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

JMS Bridge FailureStartupHandler doesn not start the SourceReceiver when the connection is established after initial startup connection failure

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 2.1.2 Final
    • Fix Version/s: 2.3.0.Beta1
    • Component/s: JMS
    • Labels:
      None

      Description

      When the HornetQ JMS Bridge starts and one the source and/or target JMS server isn't available then the bridge will start the FailureStartupHandler to try to reestablish the connection to that server.

      After the connection is successfully created then it should start SourceReceiver for receiving the Messages but it doesn't. The code for starting the SourceReceiver isn't referenced to within the FailureStartupHandler#success method.

      I provided a patch that moves the code that starts the SourceReceiver from the JMSBridge#start method to a new method called startSource(). This method is now referenced from the JMSBridge#start and the FailureStartupHandler#success method. This ensures that the SourceReceiver gets started even after the connection is reestablished.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  clebert.suconic Clebert Suconic
                  Reporter:
                  mzeijen Maurice Zeijen
                • Votes:
                  4 Vote for this issue
                  Watchers:
                  10 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: