Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-6252

Sporadic error on ssoadm commands

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 13.0.0
    • Fix Version/s: 13.5.2, 14.1.1
    • Component/s: CLI, ldapjdk
    • Labels:
    • Environment:
      Tomcat 7, JDK 8, OpenAM 13 Build 14378
    • Sprint:
      AM Sustaining Sprint 34, AM Sustaining Sprint 35, AM Sustaining Sprint 36, AM Sustaining Sprint 37, AM Sustaining Sprint 38, AM Sustaining Sprint 39, AM Sustaining Sprint 40, AM Sustaining Sprint 41
    • Story Points:
      2
    • Needs backport:
      No
    • Support Ticket IDs:
    • Needs QA verification:
      No
    • Functional tests:
      No
    • Are the reproduction steps defined?:
      No (add reasons in the comment)

      Description

      This doesn't appear to effect functionality. I'm logging this in case it is issue with the new LDAP SDK.

      I am seeing sporadic errors similar to the following. It occurred while running a scripted build based on the SE demo. Note that the agent OIDCAgent does not exist when I run this command:

      ssoadm delete-agents --verbose --agentnames OIDCAgent --realm /shop --adminid amadmin --password-file pwd.txt >/dev/null
      Identity OIDCAgent1 of type agentonly not found.
      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:275)
      	at com.sun.identity.idm.IdRepoListener.objectChanged(IdRepoListener.java:173)
      	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
      	at org.forgerock.opendj.ldap.CachedConnectionPool.getConnectionAsync(CachedConnectionPool.java:786)
      	at org.forgerock.opendj.ldap.CachedConnectionPool.getConnection(CachedConnectionPool.java:772)
      	at com.sun.identity.sm.ldap.SMDataLayer.getConnection(SMDataLayer.java:107)
      	at com.sun.identity.sm.ldap.SMSLdapObject.getConnection(SMSLdapObject.java:577)
      	at com.sun.identity.sm.ldap.SMSLdapObject.read(SMSLdapObject.java:278)
      	at com.sun.identity.sm.SMSEntry.read(SMSEntry.java:700)
      	at com.sun.identity.sm.SMSEntry.read(SMSEntry.java:677)
      	at com.sun.identity.sm.SMSEntry.<init>(SMSEntry.java:470)
      	at com.sun.identity.sm.CachedSMSEntry.getInstance(CachedSMSEntry.java:397)
      	at com.sun.identity.sm.ServiceConfigImpl.checkAndUpdatePermission(ServiceConfigImpl.java:634)
      	at com.sun.identity.sm.ServiceConfigImpl.getFromCache(ServiceConfigImpl.java:625)
      	at com.sun.identity.sm.ServiceConfigImpl.getInstance(ServiceConfigImpl.java:495)
      	at com.sun.identity.sm.ServiceConfigImpl.getInstance(ServiceConfigImpl.java:473)
      	at com.sun.identity.sm.ServiceConfigManagerImpl.getGlobalConfig(ServiceConfigManagerImpl.java:204)
      	at com.sun.identity.sm.ServiceConfigManager.getGlobalConfig(ServiceConfigManager.java:253)
      	at com.sun.identity.idm.IdUtils.initialize(IdUtils.java:128)
      	at com.sun.identity.idm.IdUtils.<clinit>(IdUtils.java:116)
      	... 5 more
      

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                gyan.baines Gyan Baines
                Reporter:
                David.Goldsmith David Goldsmith
              • Votes:
                5 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: