Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1655

JMS Connection closed after few minutes of working with business-central cluster

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.2.0.GA
    • None
    • None
    • None
    • CR2
    • Hide

      1. Setup architecture described in document
      2. Let 2 users (1 user per business central) do CRUD operations with spaces / projects / assets.

      Expected result:
      changes are replicated across cluster nodes

      Actual results:
      After a minute or two of work, the following error appears in the server.log (no additional details avaliabe :/ anywhere) :

      ERROR [org.uberfire.commons.cluster.ClusterJMSService] (default task-80) Exception on JMS broadcast: Connection is closed

      Show
      1. Setup architecture described in document 2. Let 2 users (1 user per business central) do CRUD operations with spaces / projects / assets. Expected result: changes are replicated across cluster nodes Actual results: After a minute or two of work, the following error appears in the server.log (no additional details avaliabe :/ anywhere) : ERROR [org.uberfire.commons.cluster.ClusterJMSService] (default task-80) Exception on JMS broadcast: Connection is closed

    Description

      Every time after few minutes of doing spaces / projects / assets CRUD operations, there is an exception

      "Exception on JMS broadcast: Connection is closed" after which the filesystem changes stop to be replicated across cluster nodes.

      As you can see in the setup doc, we're connecting business-central nodes to external JMS (AMQ server) using url: tcp://$AMQ_NODE_IP:61616?ha=true&retryInterval=1000&retryIntervalMultiplier=1.0&reconnectAttempts=-1

      Attachments

        Issue Links

          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. AF-1672 JMS Connection closed after few minutes of working with business-central cluster

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              aparedes@redhat.com Adriel Paredes
              jhrcek Jan Hrcek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: