HTTP 404 Error when starting Unified Self-Service 17.0

Document ID : KB000008124
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

Cannot start Unified Self-Service 17.0 and get an HTTP 404 error in the web browser. The following error appears in wrapper-tomcat.log:

agorg.apache.catalina.startup.HostConfig deployDescriptor

SEVERE: Error deploying configuration descriptor E:\Program Files\CA\Self Service\OSOP\tomcat-7.0.40\conf\Catalina\localhost\ROOT.xml

java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[]]

at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:904)

at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)

at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)

at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:657)

at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1636)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)

at java.util.concurrent.FutureTask.run(FutureTask.java:262)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at java.lang.Thread.run(Thread.java:744)

Environment:
Unified Self-Service (USS) 17.0
Cause:

While Tomcat is starting, the JAR files are scanned for multiple problems. One such problem was identified as cyclic dependency between multiple BouncyCastle JAR files. Need to add BC JAR files to the exclude list not to be scanned.

Resolution:

1. Open the catalina.properties file of USS Tomcat (i.e. C:\Program Files\CA\Self Service\OSOP\tomcat-7.0.40\conf\catalina.properties)

2. Replace the following line

tomcat.util.scan.DefaultJarScanner.jarsToSkip=\

with

tomcat.util.scan.DefaultJarScanner.jarsToSkip=bc*.jar,\

3. Start USS Services