Loading...

XML

Word

Printable

Type: Bug
Resolution: Obsolete
Priority: Major
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None
Environment:

EAP 7.2
clustered Business central
ElasticSearch 5.6.5
AMQ broker 7.2.0

Epic Link:
Business-central Authoring HA: Hardening
Steps to Reproduce:

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.
Workaround Description:

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
Docs QE Status:
NEW
QE Status:
NEW

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.

clones

RHPAM-1749 TimeoutException when logging into clustered Business central