search cancel

CA siteminder AdminUI throws Internal Server Error.

book

Article ID: 254644

calendar_today

Updated On:

Products

SITEMINDER CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder) CA Single Sign On Secure Proxy Server (SiteMinder)

Issue/Introduction

Out of memory observed in AdminUI upon deletion of a big number of objects like Domains and Policies from the AdminUI console.

After seeing the Out of memory error, If you access the AdminUI again, the admin UI returns the following error.

" Internal Server Error "

Environment

Release : 12.8.04 (12.8 SP4) and/or All the supported versions.
Operating System: Windows Server
Component : SITEMINDER WAM UI

Cause

Collect the required " smps.log ", " AdminUI server.log " and " wmicprocess " output to see the cause of the issue.

- Command to get the " wmicprocess " output:

------ wmic process where "name LIKE '%java%'" get processid,parentprocessid,executablepath,commandline 

- This " wmic " helps to monitor the system efficiently and also helps to verify the JAVA process usage by all the components within the server.

------ Analysis of the logs shows:

- From the AdminUI server log, we see the below " java OutOfMemoryError " errors.

2022-11-16 11:07:35,474 ERROR [ims.tmt.IMSMessageListener] (Thread-77 (ActiveMQ-client-global-threads)) processToEndState: Exception occured during event processing java.sql.BatchUpdateException: Java exception: 'GC overhead limit exceeded: java.lang.OutOfMemoryError'.
Caused by: java.sql.SQLException: Java exception: 'GC overhead limit exceeded: java.lang.OutOfMemoryError'.
Caused by: ERROR XJ001: Java exception: 'GC overhead limit exceeded: java.lang.OutOfMemoryError'.

------ 

If you observe the above mentioned error, please increase the JAVA heap memory in the AdminUI "standalone.conf" file (Location: XXXX\CA\siteminder\adminui\bin). (Please make sure and take the backup of the existing file before making any changes)

- Consider this as an example only:

- Existing entry in the AdminUI "standalone.conf" file:

 JAVA_OPTS="-Xms1024m -Xmx1536m -XX:MaxMetaspaceSize=256M -Djava.net.preferIPv4Stack=true"
 JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
  
- Change to below:  
   
 JAVA_OPTS="-Xms1024m -Xmx4096m -XX:MaxMetaspaceSize=256M -Djava.net.preferIPv4Stack=true -Djboss.remoting.pooled-buffers=false"
 JAVA_OPTS="$JAVA_OPTS -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true"
 
The above step helps to resolve the JAVA heap memory issue.

Also,

You may also encounter derby data related errors in the AdminUI server.log when you observe this issue.

------ AdminUI server.log:

2022-11-16 13:00:11,823 ERROR [stderr] (ServerService Thread Pool -- 286) Caused by: ERROR XJ040: Failed to start database 'D:\CA\SiteMinder\adminui/standalone/data/derby/siteminder/taskpersistence' with class loader ModuleClassLoader for Module "com.ca.iam.jdbc.derby" from local module loader @224aed64 (finder: local module finder @c39f790 (roots: D:\CA\SiteMinder\adminui\modules,D:\CA\SiteMinder\adminui\modules\system\layers\base)), see the next exception for details.

2022-11-16 13:00:11,839 ERROR [stderr] (ServerService Thread Pool -- 286)  at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)

2022-11-16 13:00:11,839 ERROR [stderr] (ServerService Thread Pool -- 286)  at org.apache.derby.impl.jdbc.SQLExceptionFactory.wrapArgsForTransportAcrossDRDA(Unknown Source)

2022-11-16 13:00:11,839 ERROR [stderr] (ServerService Thread Pool -- 286)  ... 56 more

2022-11-16 13:00:11,839 ERROR [stderr] (ServerService Thread Pool -- 286) Caused by: java.lang.ArrayIndexOutOfBoundsException: -1


2022-11-16 13:01:53,254 ERROR [io.undertow.request] (default task-1) UT005023: Exception handling request to /iam/siteminder/console/: java.lang.NullPointerException
 at com.ca.siteminder.webadmin.configuration.ui.servlet.SiteMinderLoginFilter.findEnvironment(SiteMinderLoginFilter.java:374)
 at com.ca.siteminder.webadmin.configuration.ui.servlet.SiteMinderLoginFilter.doFilter(SiteMinderLoginFilter.java:390)

Resolution

- If you observe the above mentioned error messages that means somehow the derby data got corrupted when you try to delete the domain, policies and other objects using AdminUI console so we need to perform the AdminUI re registration steps to resolve the issue.

Here derby data might get corrupted either if it went to a faulty state because of the AdminUI out of memory issue or because of the multiple restarts of the server.

If you believe the derby data got corrupted, then perform the AdminUI re registration steps by following the below document.

Take the backup of the data,log and tmp before making any changes.

- Document reference:

https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/siteminder/12-8/installing/install-the-administrative-ui/re-register-administrative-ui.html

This AdminUI re registration process helps you to resolve the above mentioned derby data related issues.

Additional Information

https://knowledge.broadcom.com/external/article/142607/error-javalangoutofmemoryerror-java-hea.html