Getting below error while starting wamui and getting unable to reach the policy server when we launch the UI url

[Viswanadha Kamballa]

Hi All,

Did anyone came across this issue in past?

I am getting below error when we register the UI and launching the URL getting policy server not reachable.

11:59:12,063 WARN [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015960: Class Path entry library/slf4j-api.jar in /opt/software/ca/wamui/siteminder/adminui/standalone/deployments/iam_siteminder.ear/user_console.war does not point to a valid jar for a Class-Path reference.
11:59:12,064 WARN [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015960: Class Path entry identityminder_ejb.jar in /opt/software/ca/wamui/siteminder/adminui/standalone/deployments/iam_siteminder.ear/user_console.war does not point to a valid jar for a Class-Path reference.
11:59:12,064 WARN [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015960: Class Path entry wpServer.jar in /opt/software/ca/wamui/siteminder/adminui/standalone/deployments/iam_siteminder.ear/user_console.war does not point to a valid jar for a Class-Path reference.
11:59:12,253 ERROR [org.wildfly.extension.undertow] (MSC service thread 1-4) Could not find tld /WEB-INF/tlds/c.tld
11:59:12,801 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.iam_siteminder.ear.config" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.
11:59:12,801 WARN [org.jboss.as.dependency.private] (MSC service thread 1-2) JBAS018567: Deployment "deployment.iam_siteminder.ear.config" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.
11:59:12,841 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.iam_siteminder.ear" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.
11:59:12,842 WARN [org.jboss.as.dependency.private] (MSC service thread 1-1) JBAS018567: Deployment "deployment.iam_siteminder.ear" is using a private module ("org.jboss.as.jmx:main") which may be changed or removed in future versions without notice.
11:59:17,210 ERROR [org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry] (MSC service thread 1-11) attributeType w/ OID 2.5.4.16 not registered!
11:59:17,757 WARN [ims.default] (MSC service thread 1-11) CA IAM Framework Server
11:59:17,757 WARN [ims.default] (MSC service thread 1-11) Copyright 2000 - 2013 CA. All Rights Reserved
11:59:17,761 WARN [ims.default] (MSC service thread 1-11) ################################################
11:59:17,761 WARN [ims.default] (MSC service thread 1-11) # IAM Framework 200.3.01.0.266
11:59:17,761 WARN [ims.default] (MSC service thread 1-11) ################################################
11:59:17,761 WARN [ims.default] (MSC service thread 1-11) ################################################
11:59:17,762 WARN [ims.default] (MSC service thread 1-11) # CA Single Sign-On 12.80.0000.1761
11:59:17,762 WARN [ims.default] (MSC service thread 1-11) ################################################
11:59:17,762 WARN [ims.default] (MSC service thread 1-11) ---- CA IAM FW Startup Sequence Initiated. ----
11:59:17,767 WARN [ims.default] (MSC service thread 1-11) * Startup Step 1 : Attempting to start ServiceLocator.
11:59:21,381 WARN [ims.default] (MSC service thread 1-11) * Startup Step 2 : Attempting to start PolicyServerService
11:59:21,382 WARN [ims.default] (MSC service thread 1-11) Unlimited Strength Java Crypto Extensions enabled: TRUE
11:59:21,409 WARN [ims.default] (MSC service thread 1-11) Policy Server connection enabled: false
11:59:21,410 WARN [ims.default] (MSC service thread 1-11) * Startup Step 3 : Attempting to start ServerCommandService
11:59:21,466 WARN [ims.default] (MSC service thread 1-11) * Startup Step 4 : Attempting to start EnvironmentService
11:59:21,468 WARN [ims.default] (MSC service thread 1-11) * Startup Step 5 : Attempting to start SecretKeyStore
11:59:21,734 ERROR [stderr] (MSC service thread 1-11) ERROR StatusLogger No log4j2 configuration file found. Using default configuration: logging only errors to the console. Set system property 'log4j2.debug' to show Log4j2 internal initialization logging.
11:59:21,744 ERROR [stderr] (MSC service thread 1-11) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found
11:59:23,134 WARN [ims.default] (MSC service thread 1-11) * Startup Step 6 : Attempting to start CacheManagerService
11:59:23,139 WARN [ims.default] (MSC service thread 1-11) * Startup Step 7 : Attempting to load global plugins.
11:59:23,142 WARN [ims.default] (MSC service thread 1-11) * Startup Step 8 : Attempting to start AdaptersConfigService
11:59:23,146 WARN [ims.default] (MSC service thread 1-11) * Startup Step 9 : Attempting to start EmailProviderService
11:59:23,171 WARN [ims.default] (MSC service thread 1-11) * Startup Step 10 : Attempting to start AuditProviderService
11:59:23,180 WARN [ims.default] (MSC service thread 1-11) * Startup Step 11 : Attempting to start RuntimeStatusDetailService
11:59:23,188 WARN [ims.default] (MSC service thread 1-11) * Startup Step 12 : Attempting to start PasswordService
11:59:23,188 WARN [ims.default] (MSC service thread 1-11) * Startup Step 13 : Attempting to start LogicalAttributeService
11:59:23,190 WARN [ims.default] (MSC service thread 1-11) * Startup Step 14 : Attempting to start BLTHService
11:59:23,190 WARN [ims.default] (MSC service thread 1-11) * Startup Step 15 : Attempting to start ParticipantResolverService
11:59:23,191 WARN [ims.default] (MSC service thread 1-11) * Startup Step 16 : Attempting to start NotificationRuleService
11:59:23,191 WARN [ims.default] (MSC service thread 1-11) * Startup Step 17 : Attempting to start EventAdapterService
11:59:23,191 WARN [ims.default] (MSC service thread 1-11) * Startup Step 18 : Attempting to start TaskService
11:59:23,197 WARN [ims.default] (MSC service thread 1-11) * Startup Step 19 : Attempting to start WorkflowCallbackService
11:59:23,199 WARN [ims.default] (MSC service thread 1-11) * Startup Step 20 : Attempting to start WorkflowService
11:59:23,203 WARN [ims.default] (MSC service thread 1-11) * Startup Step 21 : Attempting to start TaskStatusNotifyService
11:59:23,204 WARN [ims.default] (MSC service thread 1-11) * Startup Step 22 : Attempting to start EventService
11:59:23,222 WARN [ims.default] (MSC service thread 1-11) * Startup Step 23 : Attempting to start AdminService
11:59:23,223 WARN [ims.default] (MSC service thread 1-11) * Startup Step 24 : Attempting to start GeneralMonitorAdmin
11:59:23,224 WARN [ims.default] (MSC service thread 1-11) * Startup Step 25 : Attempting to start GlobalInitializer plug-ins
11:59:23,224 WARN [ims.default] (MSC service thread 1-11) * Startup Step 26 : Attempting to start SchedulerService
11:59:23,369 WARN [ims.default] (MSC service thread 1-11) * Startup Step 27 : Attempting to start environments
11:59:23,383 WARN [ims.default] (MSC service thread 1-11) ** FIPS mode enabled : false
11:59:23,388 WARN [ims.default] (MSC service thread 1-11) * Startup Step 28 : Attempting to recover unprocessed events and runtime status details
11:59:23,389 WARN [ims.default] (MSC service thread 1-11) * Startup Step 29 : Attempting to start ApplicationContextInitializer plug-ins


Thanks,
Viswanadha.

[Osarobo Idehen]

Hello Viswanadha, 

I would recommend you to open a support case and update the case with the Adminui server.log and boot.log and the policy server logs if you are not able to access your AdminUI.

Thanks

Osarobo

[Nazeer Ahmed]

Hi, 
What could be the solution for the above issue? I'm facing exactly the same issue.

Regards,
Nazeer

------------------------------
Lead
ADP
------------------------------

[Nazeer Ahmed]

Hi,
Have you found a solution for the above issue? I'm getting the same issue now. Any quick help will be more grateful.

Thanks,
Nazeer

------------------------------
Lead
ADP
------------------------------

[Sneha Kasireddy]

​Hello All,

I am facing similar issue. Please share us resolution for this issue.

Thanks,
Sneha

[Patrick Dussault]

Hi Sneha,

The following errors are cosmetics and should not harm the usage of
the AdminUI, as I get the same in my AdminUI 12.8SP3 on RedHat 7 :

08:26:34,661 ERROR [org.wildfly.extension.undertow] (MSC service
thread 1-1) Could not find tld /WEB-INF/tlds/c.tld

08:26:45,612 ERROR
[org.apache.directory.server.schema.registries.DefaultAttributeTypeRegistry]
(MSC service thread 1-2) attributeType w/ OID 2.5.4.16 not
registered!

08:26:46,981 ERROR [stderr] (MSC service thread 1-2) ERROR
StatusLogger No log4j2 configuration file found. Using default
configuration: logging only errors to the console. Set system
property 'log4j2.debug' to show Log4j2 internal initialization
logging.

08:26:47,006 ERROR [stderr] (MSC service thread 1-2)
ScriptEngineManager providers.next():
javax.script.ScriptEngineFactory: Provider
com.sun.script.javascript.RhinoScriptEngineFactory not found

08:26:50,325 ERROR [stderr] (MSC service thread 1-2)
ScriptEngineManager providers.next():
javax.script.ScriptEngineFactory: Provider
com.sun.script.javascript.RhinoScriptEngineFactory not found

and I can login and browse the AdminUI without issue.

At the beginning of this Thread, Viswanadha mentioned that the issue
was "when we register the UI and launching the URL getting policy
server not reachable".

As such, the problem is in communication with the Policy Server.

As running AdminUI on Linux, you should pay attention to some prereq :

- Have enough entropy on the system :

Increase Entropy

Install Required Korn Shell (ksh) Package on Linux

Configure Security–Enhanced Linux (SELinux) to Work with CA Single Sign-on

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-identity-and-access-management/single-sign-on/12-8-03/installing/install-the-administrative-ui/install-the-administrative-ui-on-linux-stand-alone.html

- More, insure that :

- The OS firewall let communication between the AdminUI and Policy Server;
- The Policy Server runs on default ports as 44441 44442 44443;
- If both Policy Server and AdminUI runs on the same machine,
AdminUI runs with a different user as the Policy Server;

I hope this helps,

Best Regards,
Patrick