Solutions
Archived

java.lang.ExceptionInInitializerError when using ssoadm commands in AM 5, 5.1 and OpenAM 13, 13.5, 13.5.1

Last updated Apr 12, 2021

The purpose of this article is to provide assistance if you receive an "Exception in thread "SystemTimer" java.lang.Error: java.lang.ExceptionInInitializerError" error when using ssoadm commands in AM/OpenAM. This error occurs even though the ssoadm response indicates the operation was successful and shows as "caused by: java.lang.IllegalStateException: CachedConnectionPool is already closed".


1 reader recommends this article

Archived

This article has been archived and is no longer maintained by ForgeRock.

Symptoms

The following error is sporadically shown when some ssoadm commands are run, even though you will see a positive response (for example, Schema attribute defaults were set).

Exception in thread "SystemTimer" java.lang.Error: java.lang.ExceptionInInitializerError at com.sun.identity.common.TimerPool$WorkerThread.run(TimerPool.java:542) Caused by: java.lang.ExceptionInInitializerError at com.sun.identity.idm.IdRepoListener.getChangedIds(IdRepoListener.java:278) at com.sun.identity.idm.IdRepoListener.objectChanged(IdRepoListener.java:174) at com.sun.identity.idm.remote.IdRemoteEventListener.sendIdRepoNotification(IdRemoteEventListener.java:315) at com.sun.identity.idm.remote.IdRemoteEventListener$NotificationRunnable.run(IdRemoteEventListener.java:398) at com.sun.identity.common.TimerPool$WorkerThread.run(TimerPool.java:434) Caused by: java.lang.IllegalStateException: CachedConnectionPool is already closed

Recent Changes

Upgraded to, or installed AM 5 or 5.1.

Upgraded to, or installed OpenAM 13, 13.5 or 13.5.1.

Causes

When the ssoadm command is executed, the polling thread tries to retrieve the changes from the server, but ssoadm starts to shut the process down before the changes are retrieved. This timing issue causes the error but the ssoadm operation itself completes successfully.

Solution

Firstly, these errors can be safely ignored since the operation performed by ssoadm still completes successfully.

However, this issue can be resolved by upgrading to AM 5.1.1 or later, or OpenAM 13.5.2; you can download this from BackStage.

See Also

Policy import fails in OpenAM 13.0 with Invalid resource type null message

FAQ: Installing and using ssoadm in AM

Related Training

N/A

Related Issue Tracker IDs

OPENAM-6252 (Sporadic error on ssoadm commands)

OPENAM-7852 (Various list-xxx ssoadm commands fail)


Copyright and Trademarks Copyright © 2021 ForgeRock, all rights reserved.