Problems with Administrative UI after installation

Products

• CA Single Sign-On
• SITEMINDER

Issue/Introduction

We have performed the installation of AdminUI, registered it with our Policy Server, and it starts correctly but after some time it begins to fail returning HTTP 404 errors.

Afterwards, it does not restart correctly anymore unless it is reinstalled.

How can we solve this issue?

Environment

Applies the SiteMinder AdminUI any version

Applies to Any Linux OS

Cause

This problem was caused as the open files limit in the OS was reached and AdminUI failed to open some files needed:

2018-07-10 16:41:16,244 WARN  [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$WildFlyLocalMCF] (ConnectionValidator) Destroying connection that is not valid, due to the following exception: org.apache.derby.impl.jdbc.EmbedConnection40@613608241 (XID = null), (SESSIONID = 1), (DATABASE = /opt/siteminder/adminui/standalone/data/derby/siteminder/taskpersistence), (DRDAID = null) : java.sql.SQLException: Meta-data for Container org.apache.derby.impl.store.raw.data.RAFContainer4@346ea6d1 could not be accessed 
... 
Caused by: java.sql.SQLException: Java exception: '/opt/siteminder/adminui/standalone/data/derby/siteminder/taskpersistence/seg0/c2f0.dat (Too many open files): java.io.FileNotFoundException'. 

Then other errors followed causing the HTTP 404 errors. During the startup of the AdminUI there is a warning letting you know that the current open file limit is set too low:

2018-07-10 16:07:04,356 WARN  [org.jboss.as.warn.fd-limit] (main) JBAS015972: The operating system has limited the number of open files to 1024 for this process; a value of at least 4096 is recommended 

Resolution

Verify the ulimit open files limit by running this command as the same user that starts the AdminUI.

# ulimit -a 

In this scenario, the user was limited to the system default of 1024.

Work with your Linux administrators to permanently increase the open files limit for the the AdminUI starting user.