Uploaded image for project: 'OpenIDM'
  1. OpenIDM
  2. OPENIDM-6656

Random error during startup causes startup fail or longer time to get ready

    Details

      Description

      From time to time, see the following errors in IDM startup. The startup is either failed or took longer time for IDM to get ready(e.g. 4 minutes).

      SEVERE: Bundle: org.forgerock.openidm.audit [138] [org.forgerock.openidm.audit.filter(21)] Circular reference detected, getService returning null
      Sep 15, 2016 6:04:44 PM org.forgerock.openidm.logging.LogServiceTracker logEntry
      SEVERE: Bundle: org.forgerock.openidm.api-servlet [44] FrameworkEvent ERROR
      org.apache.felix.log.LogException: org.osgi.framework.ServiceException: Service factory returned null. (Component: org.forgerock.openidm.audit.filter (21))
              at org.apache.felix.framework.ServiceRegistrationImpl.getFactoryUnchecked(ServiceRegistrationImpl.java:380)
      ...
      
      Sep 15, 2016 6:07:01 PM org.forgerock.openidm.quartz.impl.RepoJobStore getTriggerGroupNames
      WARNING: Error getting trigger group names
      org.forgerock.json.resource.ServiceUnavailableException: Service is starting
              at org.forgerock.openidm.filter.ServiceUnavailableFilter.<init>(ServiceUnavailableFilter.java:43)
              at org.forgerock.openidm.servlet.internal.ServletConnectionFactory.<clinit>(ServletConnectionFactory.java:96)
              at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
              at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
              at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
              at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
              at java.lang.Class.newInstance(Class.java:442)
      ...
      Sep 15, 2016 6:07:08 PM org.forgerock.openidm.info.impl.HealthService setState
      INFO: OpenIDM ready
      

      Note: The full IDM log is attached, it's a run with Kerberized DB2.
      I first saw this symptom was with master build 1785 used Postgres.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                dhogan Dirk Hogan
                Reporter:
                Tinghua.Xu Tinghua Xu
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: