Uploaded image for project: 'Spring Integration'
  1. Spring Integration
  2. INT-552

ActiveMQ Recovery

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Complete
    • Affects Version/s: 1.0.1
    • Fix Version/s: 2.2. GA
    • Component/s: None
    • Labels:
      None

      Description

      Currently when activemq connection fails, the failover tries to reconnect and the jms-adapters are in stand-by. When the app reconnects, all the adapters continue sending messages.

      But, when we process an external call to our si system with the connection broken, the process stops in the jms-adapters. If we kill our process the call is never processed again.

      Attached a eclipse java project (maven2 && spring integration) showing an example. The steps of the process are:

      1- Reads a file
      2- Gets the file name and rename the file
      3 -Sends the file name to an activemq queue

      If we stop our activemq and then kill the process, the file is renamed and we never process it again.

      Right now we can handle this issue creating more channels (i.e. between step 2 and 3 one channel persisted on activemq queue with a service activator endpoint which renames the file).

        Attachments

          Activity

            People

            Assignee:
            abilan Artem Bilan
            Reporter:
            nestabur Nestor Tarin Burriel
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: