12.8sp5 admin ui WARNs and ERRORs on startup

Products

SITEMINDER CA Single Sign On Agents (SiteMinder)

Issue/Introduction

There are many WARNs and ERRORs during 12.8sp5 admin ui startup.

We need clean them up or provide explanation.

Some of the errors for example from server.log:

ERROR [stderr] (MSC service thread 1-4) ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...
ERROR [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0074: Could not find TLD /WEB-INF/tlds/c.tld
ERROR [org.apache.directory.api.ldap.model.entry.DefaultAttribute] (ServerService Thread Pool -- 70) ERR_13208_ATTRIBUTE_IS_SINGLE_VALUED The attribute 'm-description' is single valued, we can't add no more values into it
ERROR [ims.Main] (ServerService Thread Pool -- 70) alias_report_ds is not defined.

....

Environment

Release : 12.8.05

Component : SITEMINDER WAM UI

Cause

These WARNs and ERRORs are cosmetic, should not impact the product's functionality.

However, engineering acknowledges this integration could be cleaner.

Resolution

Please apply the suggested mitigation steps to 12.8sp5 admin ui only.

1) 15:26:38,856 WARN [org.jboss.weld.deployer] (MSC service thread 1-3) WFLYWELD0007: Could not load portable extension class org.hibernate.validator.cdi.ValidationExtension: javax.validation.NoProviderFoundException: Unable to create a Configuration, because no Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath.
at javax.validation.Validation$GenericBootstrapImpl.configure(Validation.java:291)
at org.hibernate.validator.cdi.ValidationExtension.<init>(ValidationExtension.java:112)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

2) 06:28:37,726 WARN [org.jboss.as.jaxrs] (MSC service thread 1-4) WFLYRS0018: Explicit usage of Jackson annotation in a JAX-RS deployment; the system will disable JSON-B processing for the current deployment. Consider setting the 'resteasy.preferJacksonOverJsonB' property to 'false' to restore JSON-B.

For the above 2 Warnings, the Solution is:

Go to the <Admin-UI-Installed-Location>/adminui/standalone/deployments/iam_siteminder.ear/META-INF.

Take backup of the existing file named "jboss-deployment-structure.xml". Add the below "weld" and "jaxrs" subsystems in the <exclude-subsystem> as below

<exclude-subsystems>
<subsystem name="weld"/>

3) 5:26:38,068 WARN [org.jboss.as.dependency.private] (MSC service thread 1-4) WFLYSRV0018: Deployment "deployment.iam_siteminder.ear" is using a private module ("org.jboss.as.jmx") which may be changed or removed in future versions without notice.

For the above Warning, the Solution is.

Go to the <Admin-UI-Installed-Location>/adminui/standalone/deployments/iam_siteminder.ear/META-INF

Open the jboss-deployment-structure.xml. Remove/Comment the " org.jboss.as.jmx " module from the dependencies as below.

4)15:26:24,306 ERROR [stderr] (MSC service thread 1-1) ERROR StatusLogger Log4j2 could not find a logging implementation. Please add log4j-core to the classpath. Using SimpleLogger to log to the console...

For the above ERROR, the Solution is.

Go to the <Admin-UI-Installed-Location>/adminui/modules/com/ca/iam/log4j2/core/main

Take backup of the existing "module.xml".

Open the module.xml. Add the below highlighted entries and save it.

<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.1" name="com.ca.iam.log4j2.core">
<resources>
<resource-root path="log4j-core-2.12.0.jar"/>
<resource-root path="log4j-api-2.12.0.jar"/>
<resource-root path="."/>
</resources>
</module>

Copy the log4j-api-2.12.0.jar from "<Admin-UI-Installed-Location>/adminui//standalone/deployments/iam_siteminder.ear/library" to the "<Admin-UI-Installed-Location>/adminui/modules/com/ca/iam/log4j2/core/main" location.

Copy the log4j_jboss.properties from the location "<Admin-UI-Installed-Location>\adminui\standalone\deployments\iam_siteminder.ear\config\com\netegrity\config to the
"<Admin-UI-Installed-Location>/adminui/modules/com/ca/iam/log4j2/core/main" location.

Rename it as "log4j2.properties".

Go to the <Admin-UI-Installed-Location>/adminui/modules/com/ca/iam/idmutils\main .

Take backup of the existing "module.xml".

Open the module.xml. Remove/Comment out the below highlighted entry and save it.

Stop and Start the Adminui, verify all the above WARNING and ERROR are no logging in to the server.log.

After the above steps, there may be remaining WARNs and last ERROR left as below.

Djboss.server.base.dir="<Admin-UI-Installed-Location>/adminui/siteminder/adminui/standalone" " -c standalone-full.xml -b 0.0.0.0 -Dnete.j2ee.vendor=jboss -Djboss.as.management.blocking.timeout=900"
=========================================================================

11:17:21,744 WARN [org.apache.activemq.artemis.jms.server] (ServerService Thread Pool -- 51) AMQ122005: Invalid "host" value "0.0.0.0" detected for "http-connector" connector. Switching to "www.example.net". If this new address is incorrect please manually configure the connector to use the proper one.
11:17:30,673 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) WFLYSRV0018: Deployment "deployment.iam_siteminder.ear.user_console.war" is using a private module ("org.jboss.as.connector") which may be changed or removed in future versions without notice.
11:17:34,285 ERROR [org.apache.directory.api.ldap.model.entry.DefaultAttribute] (ServerService Thread Pool -- 57) ERR_13208_ATTRIBUTE_IS_SINGLE_VALUED The attribute 'm-description' is single valued, we can't add no more values into it

There remaining WARN/ERROR can not be fixed for now, as it needs to go through much more regression testing. Customer can document remaining error as exceptions and solution will be deferred to future Siteminder release.

Additional Information

This defect is fixed in subsequent 12.8sp6 admin ui. Please see release note:

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/siteminder/12-8/release-notes/service-packs/defects-fixed-in-12-8-06.html

32655802

DE500440

Administrative UI startup logs contain the following WARNING messages that do not impact the Administrative UI initiation:

Could not load portable extension class org.hibernate.validator.cdi.ValidationExtension: javax.validation.NoProviderFoundException
Explicit usage of Jackson annotation in a JAX-RS deployment; the system will disable JSON-B processing for the current deployment