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

TimeoutException when logging into clustered Business central

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.6.0.GA
    • 7.2.0.GA
    • Business Central

    • EAP 7.2
      clustered Business central
      ElasticSearch 5.6.5
      AMQ broker 7.2.0

    • Release Notes
    • CR1
    • CR1
    • Hide

      Allow concurrent access to the replication cache by following https://access.redhat.com/solutions/2776221

      Show
      Allow concurrent access to the replication cache by following https://access.redhat.com/solutions/2776221
    • Hide

      Install and start clustered Business central using documented approach - with ElasticSearch, AMQ and 2 standalone Business central nodes. The Business centrals need to have <distributable/> tag uncommented.
      Log into one of the nodes.

      Show
      Install and start clustered Business central using documented approach - with ElasticSearch, AMQ and 2 standalone Business central nodes. The Business centrals need to have <distributable/> tag uncommented. Log into one of the nodes.
    • 2019 Week 44-46 (from Okt 28)

      The issue happens on clustered Business central instance.
      When user tries to log into Business central node an exception is thrown, see attachment.

      When workaround described in https://access.redhat.com/solutions/2776221 was applied then user is able to log in.

        1. stacktrace.txt
          121 kB

            aparedes@redhat.com Adriel Paredes
            ksuta Karel Suta
            Karel Suta Karel Suta
            Karel Suta Karel Suta
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: