Previous Topic: Ignore the Error Table osop.Lock_does not Exist in Liferay LogNext Topic: Onboarding a Tenant Throws Tomcat Error


CA EEM Errors in FIPS Mode

Symptom:

When I work with FIPS mode supported CA Open Space, CA EEM API displays the following logs messages:

log4j:WARN Continuable parsing error 1 and column 20
log4j:WARN Document root element "EiamConfiguration", must match DOCTYPE root "null".
log4j:WARN Continuable parsing error 1 and column 20
log4j:WARN Document is invalid: no grammar found.
log4j:ERROR DOM element is - not a <log4j:configuration> element.

Solution:

CA Open Space does not have a control over these logs and it does not affect any functionality of CA EEM.