Unified Self-Service (USS) page cant be found and/or HTTP 404 Not Found

book

Article ID: 5090

calendar_today

Updated On:

Products

CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

Unified Self-Service (USS) page can’t be found and/or HTTP 404 Not Found

<Please see attached file for image>

1a.png

 

<Please see attached file for image>

2.png

 

The USS Tomcat java.exe process does not reach expected amount of memory (~1.2GB), but it limits to ~900MB;

<Please see attached file for image>

3.png

<Please see attached file for image>

4.png

 

Similiar errors could appear at USS Tomcat log file ("wrapper-tomcat") located under “{USS_home}\OSOP\tomcat-7.0.40\logs”:

 

SEVERE: Exception sending context initialized event to listener instance of class com.liferay.portal.spring.context.PortalContextLoaderListener

 

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.liferay.portal.spring.aop.ServiceBeanAutoProxyCreator#0' defined in class path resource [META-INF/base-spring.xml]: Cannot resolve ...

 

Similar errors could appear in USS Liferay log files ("") located under “{USS_Home}\OSOP\logs”:

 

java.sql.SQLException: ORA-28001: the password has expired

Cause

Liferay Logs (in: C:\Program Files\CA\Self Service\OSOP\logs\Liferay.xxxxxx) would contain some explanation around why the USS app is not starting fully.

 

See couple of examples below: 

1) Error about database password expiry:

03:09:07,490 WARN  [BasicResourcePool:1841] [email protected]af -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception:

 

java.sql.SQLException: ORA-28001: the password has expired

 

In this case, the reason appears to be simply that the password for "ussdbadmin" db user is expired.   Fixing that issue in the database should help out with the resolution.

 

 

 

2) Error about database connection:

17:11:30,494 WARN  [BasicResourcePool:1841] [email protected]3b -- Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (30). Last acquisition attempt exception: 

java.sql.SQLException: Unknown server host name 'MY_Database_SQL_Server'.

               at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:401)

               at net.sourceforge.jtds.jdbc.ConnectionJDBC3.<init>(ConnectionJDBC3.java:50)

               at net.sourceforge.jtds.jdbc.Driver.connect(Driver.java:184)

               at com.mchange.v2.c3p0.DriverManagerDataSource.getConnection(DriverManagerDataSource.java:134)

               at com.mchange.v2.c3p0.WrapperConnectionPoolDataSource.getPooledConnection(WrapperConnectionPoolDataSource.java:182)

               at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool$1PooledConnectionResourcePoolManager.acquireResource(C3P0PooledConnectionPool.java:148)

               at com.mchange.v2.resourcepool.BasicResourcePool.doAcquire(BasicResourcePool.java:1014)

               at com.mchange.v2.resourcepool.BasicResourcePool.access$800(BasicResourcePool.java:32)

               at com.mchange.v2.resourcepool.BasicResourcePool$AcquireTask.run(BasicResourcePool.java:1810)

               at com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:547)

Caused by: java.net.UnknownHostException: MY_Database_SQL_Server

               at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178)

               at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)

               at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)

               at java.net.Socket.connect(Socket.java:579)

               at sun.reflect.GeneratedMethodAccessor32.invoke(Unknown Source)

               at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

               at java.lang.reflect.Method.invoke(Method.java:606)

               at net.sourceforge.jtds.jdbc.SharedSocket.createSocketForJDBC3(SharedSocket.java:307)

               at net.sourceforge.jtds.jdbc.SharedSocket.<init>(SharedSocket.java:257)

               at net.sourceforge.jtds.jdbc.ConnectionJDBC2.<init>(ConnectionJDBC2.java:311)

               ... 9 more

 

 

In this case, the reason appears to be that USS is not able to find the database host defined in the portal-ext.properties file.  Open the file and look for the JDBC entry like below:

jdbc.default.url=jdbc:jtds:sqlserver://MY_Database_SQL_Server:1433/USS_mdb

Correct the My_Database_SQL_Server  to the correct node name and restart CA Unified Self Service service.

 

 

 

Environment

CA Service Management 14.1Unified Self-Service

Resolution

Check the resolutions indicated in the Cause Section above and restart CA Unified Self Service server.

Attachments

1558693669121000005090_sktwi1f5rjvs16mbl.png get_app
1558693667354000005090_sktwi1f5rjvs16mbk.png get_app
1558693665518000005090_sktwi1f5rjvs16mbj.png get_app
1558693663880000005090_sktwi1f5rjvs16mbi.png get_app