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

output from re-indexing action during initial configuration is lost

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 11.0.0, 11.0.1, 11.0.2, 11.0.3, 12.0.0, 12.0.1, 12.0.2, 12.0.3, 12.0.4, 13.0.0, 13.5.0
    • Fix Version/s: 13.5.1, 14.5.0, 14.1.2
    • Component/s: configurator
    • Labels:
    • Environment:
    • Sprint:
      AM Sustaining Sprint 34, AM Sustaining Sprint 35, AM Sustaining Sprint 36, AM Sustaining Sprint 37
    • Story Points:
      3
    • Support Ticket IDs:

      Description

      When configuring OpenAM (with silent input file ) using configurator.jar there is a time where no progress is logged after service schema ldif's are loaded

      excerpt from install log
      ...
      Loading Schema opendj_oathdevices.ldif...Success.
      

      eventually

      ...Success.
      

      is logged.

      Only when the JVM-Options _ -Dcom.iplanet.services.debug.level=message -Dcom.iplanet.services.debug.directory=WRITABLE_EXISTING_DIRECTORY'_ are set during initial configuration one gets a clue what's happening,

      excerpt from OpenAM debug logs
      amSetupServlet:11/22/2016 09:57:55:737 PM CET: Thread[http-nio-8181-exec-2,5,main]: TransactionId[9cce1004-d1dd-4e89-a4b8-92a86f8e0f20-3]
      EmbeddedOpenDS.shutdown server...
      amSetupServlet:11/22/2016 09:58:00:771 PM CET: Thread[http-nio-8181-exec-2,5,main]: TransactionId[9cce1004-d1dd-4e89-a4b8-92a86f8e0f20-3]
      EmbeddedOpenDS.shutdown server success.
      amSetupServlet:11/22/2016 09:58:01:439 PM CET: Thread[http-nio-8181-exec-2,5,main]: TransactionId[9cce1004-d1dd-4e89-a4b8-92a86f8e0f20-3]
      EmbeddedOpenDS:rebuildIndex:Result:
      amSetupServlet:11/22/2016 09:58:01:439 PM CET: Thread[http-nio-8181-exec-2,5,main]: TransactionId[9cce1004-d1dd-4e89-a4b8-92a86f8e0f20-3]
      EmbeddedOpenDS.startServer(/Users/bt114760/Documents/projects/ForgeRock/Support/Tickets/16654/heimdallr1/opends)
      amSetupServlet:11/22/2016 09:58:01:439 PM CET: Thread[http-nio-8181-exec-2,5,main]: TransactionId[9cce1004-d1dd-4e89-a4b8-92a86f8e0f20-3]
      EmbeddedOpenDS.startServer:starting DS Server...
      amSetupServlet:11/22/2016 09:58:02:031 PM CET: Thread[http-nio-8181-exec-2,5,main]: TransactionId[9cce1004-d1dd-4e89-a4b8-92a86f8e0f20-3]
      ...EmbeddedOpenDS.startServer:DS Server started.
      

      However the output from the re-index task seems to be lost, which is indicated by

      amSetupServlet:11/22/2016 09:58:01:439 PM CET: Thread[http-nio-8181-exec-2,5,main]: TransactionId[9cce1004-d1dd-4e89-a4b8-92a86f8e0f20-3]
      EmbeddedOpenDS:rebuildIndex:Result:
      

      If some error occurs then this error/exception seems to be lost as well and OpenAM configuration is not finished and nothing happens anymore. This is indicated by the following in the install log

      excerpt from install log
      ...
      Loading Schema opendj_oathdevices.ldif...Success.
      

      --> This is the last entry in the log!

      The root cause why the configuration failed can not be determined as OpenDJ log files also do not show anything and there is also no indicator / stacktrace in Tomcat log.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                markdr Mark de Reeper
                Reporter:
                bthalmayr Bernhard Thalmayr
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: