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

ssoadm fails on multi-core machines

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Critical
    • Resolution: Duplicate
    • Affects Version/s: 13.5.0
    • Fix Version/s: None
    • Component/s: CLI
    • Labels:
      None
    • Environment:
      Server with 40 CPUs or more (using 'lscpu' on Linux)

      Some Linux

      OpenAM 13.5.0
    • Support Ticket IDs:

      Description

      When running ssoadm on a machine with lots of CPUs/Cores , ssoadm bails out with the following error

      Exception in thread "pool-4-thread-1" java.lang.OutOfMemoryError: unable to create new native thread
      	at java.lang.Thread.start0(Native Method)
      	at java.lang.Thread.start(Thread.java:714)
      	at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:336)
      	at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:191)
      	at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:64)
      	at java.lang.Thread.run(Thread.java:745)
      

      Most likely this is because Apache http client is now initialised as part of the audit framework in SMSEmbeddedLdapObject , so the following blog is quite interesting

      https://beachape.com/blog/2013/09/12/resolving-java-oom-unable-to-create-new-native-thread-errors-on-heroku/

      It's also interesting that ssoadm uses SMSEmbeddedLdapObject although ssoadm is not running in the same JVM as OpenDJ as it would be the when OpenDJ is used as embedded OpenAM configuration data store, so it should actually use SMSLdapObject, shouldn't it?

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                peter.major Peter Major [X] (Inactive)
                Reporter:
                bthalmayr Bernhard Thalmayr
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: