search cancel

Process Automation - Login page not shown after installing

book

Article ID: 202402

calendar_today

Updated On:

Products

CA Process Automation Base Process Automation Manager

Issue/Introduction

After recently installing Process Automation, the login page is not shown.

Cause

Reviewing c2o.log the following it's shown:

 INFO  [com.optinuity.c2o.server.ServerController] [           main] Time taken for DBAdjustment : PAMJMSQueuesDB53 ms.
 INFO  [com.optinuity.c2o.server.ServerController] [           main] DDL update completed
 ERROR [com.optinuity.c2o.c2oserver.ServerManager] [      Thread-13] Unable to start ActiveMQ or it has been stopped...
 ERROR [com.optinuity.c2o.c2oserver.ServerManager] [      Thread-13] PAM Server will shut down now

This means ActiveMQ had an issue while booting. Reviewing ActiveMQ logs, the following error appears:

"Starting ActiveMQ with JAVA_HOME->""c:\program files\java\jdk1.8.0_261\jre"
INFO | OasisConfig.properties path============== E:\Program Files\CA\PAM\activemq\bin\..\..\server\c2o\.config\OasisConfig.properties
INFO | -------Value of property ---- org.bouncycastle.rsa.allow_multi_use true
Exception in thread "main" java.lang.ExceptionInInitializerError

Caused by: java.lang.RuntimeException: java.security.NoSuchAlgorithmException: Service not registered with Provider BCFIPS: BCFIPS: SecureRandom.DEFAULT -> org.bouncycastle.jcajce.provider.random.DefSecureRandom
attributes: {ImplementedIn=Software}

Environment

Process Automation - 4.3 SP3 and above

Resolution

This means that a wrong/unsupported release of JDK was installed on Process Automation server.

The following article explains what JDK version can be used up to PAM 4.3.05:

Java Compatibility with IT Process Automation

In order to solve this issue, the current JDK release must be downgrade to JDK to 1.8.0_192, that's the newest Java release that has been tested successfully with PAM 4.3.05.

Once the suggested JDK is installed, Process Automation must be pointed to use this new Java release installed, as per the following article:

How to verify, upgrade or change the Java JDK being used by Process Automation.