An AdminUI observed errors and exception in the AdminUI
server.log as :
2020-08-24 19:40:20,441 ERROR [stderr] (MSC service thread 1-2)
ERROR StatusLogger Log4j2 could not find a logging
implementation. Please add log4j-core to the classpath. Using
SimpleLogger to log to the console...
2020-08-24 19:40:26,455 ERROR [org.wildfly.extension.undertow] (MSC
service thread 1-7) WFLYUT0074: Could not find TLD
/WEB-INF/tlds/c.tld
2020-08-24 19:40:30,311 ERROR
[org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry]
(ServerService Thread Pool -- 115) attributeType w/ OID 2.5.4.16 not
registered!
2020-08-24 19:40:33,074 ERROR [ims.Main] (ServerService Thread Pool
-- 115) alias_report_ds is not defined.
AdminUI 12.8SPx on RedHat 7.x;
The AdminUI reports 4 ERROR :
server.log
2020-08-24 19:40:20,441 ERROR [stderr] (MSC service thread 1-2)
ERROR StatusLogger Log4j2 could not find a logging
implementation. Please add log4j-core to the classpath. Using
SimpleLogger to log to the console...
2020-08-24 19:40:26,455 ERROR [org.wildfly.extension.undertow] (MSC
service thread 1-7) WFLYUT0074: Could not find TLD
/WEB-INF/tlds/c.tld
2020-08-24 19:40:30,311 ERROR
[org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry]
(ServerService Thread Pool -- 115) attributeType w/ OID 2.5.4.16 not
registered!
2020-08-24 19:40:33,074 ERROR [ims.Main] (ServerService Thread Pool
-- 115) alias_report_ds is not defined.
About the error :
"alias_report_ds is not defined"
This error won't harm the functionalities of AdminUI and can be ignored.
Conclusion
The AdminUI Framework has multiple data sources and alias_report_ds is used for reporting JNDI data source connection which is not defined into standalone.xml hence we are getting this error. Siteminder is not using reports API hence we can ignore this error.