[OPENAM-13438] Setting org.forgerock.openam.ldap.heartbeat.timeout=-1 makes AM unusable Created: 13/Aug/18  Updated: 02/Jul/19  Resolved: 27/Sep/18

Status: Closed
Project: OpenAM
Component/s: CTS
Affects Version/s: 5.5.1, 6.0.0,,,
Fix Version/s:, 6.5.0, 6.0.1, 5.5.2

Type: Bug Priority: Major
Reporter: Bernhard Thalmayr Assignee: Adam Heath
Resolution: Fixed Votes: 0
Labels: EDISON
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Oracle JDK 1.8.0_151-b12
Apache Tomcat/9.0.8

Issue Links:
is related to OPENAM-13648 Provide input validation when updatin... Open
Target Version/s:
Rank: 1|hzwi87:
Sprint: AM Sustaining Sprint 54, AM Sustaining Sprint 55
Story Points: 2
Needs backport:
QA Assignee: Filip Kubáň [X] Filip Kubáň [X] (Inactive)
Verified Version/s:
Needs QA verification:
Functional tests:
Are the reproduction steps defined?:
Yes and I used the same an in the description


Bug description

_AM becomes unusable when setting advanced server property _

How to reproduce the issue

  1. Initially Configure AM
  2. set advanced property "org.forgerock.openam.ldap.heartbeat.timeout=-1" in server-defaults
  3. restart AM deployment container
  4. after restart try to access AM console
Expected behaviour
XUI-based authentication screen should be seen
Current behaviour
blank page shows up

Work around

to get out of this situation the related attribute has to be corrected via ldapmodify in the embedded configuraton data store.

Comment by Adam Heath [ 26/Sep/18 ]

Fixes in https://stash.forgerock.org/projects/OPENAM/repos/openam/pull-requests/5695/overview will address the issue of AM becoming unstable. As part of the review it has been suggested that there should possibly be some further validation of the advanced properties at the point of entry to provide some useful feedback to the user at the time they try to update this - this will addressed in a separate set of changes.

See https://bugster.forgerock.org/jira/browse/OPENAM-13648

Comment by Filip Kubáň [X] (Inactive) [ 12/Oct/18 ]

verified on ForgeRock Access Management Build 70748811ef (2018-October-12 05:22)

Am is usable after container restart.

Comment by Ľubomír Mlích [ 02/Jul/19 ]

Reproduced in ForgeRock Access Management 5.5.1 Build 96b47ad4f1 (2017-October-26 15:41) - I see blank page and HTTP 500 in network tools with stacktrace
Verified in ForgeRock Access Management 5.5.2-M5 Build 9fbbb857d0 (2019-June-27 13:27) - No blank page, I can login

Comment by Ľubomír Mlích [ 02/Jul/19 ]

No more verification

Generated at Sun May 16 16:07:09 UTC 2021 using Jira 8.16.0#816000-sha1:a455b91378454416b49bbc88d03e653cb9815ed5.