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

IDM 4.5.1 fails to start when Oracle or DB2 is used as repo

    XMLWordPrintable

    Details

      Description

      When used oracle DB as repo, IDM 4.5.1 failed to start, IDM logged the following error(the complete log is attached):
      Jan 13, 2017 6:09:38 PM org.forgerock.openidm.config.persistence.RepoPersistenceManager$1 hasMoreElements
      WARNING: Failure getting configuration dictionaries for hasMoreElements DB reported failure executing query.
      org.forgerock.json.resource.InternalServerErrorException: DB reported failure executing query.
      at org.forgerock.openidm.repo.jdbc.impl.query.TableQueries.query(TableQueries.java:353)
      at org.forgerock.openidm.repo.jdbc.impl.GenericTableHandler.query(GenericTableHandler.java:625)
      at org.forgerock.openidm.repo.jdbc.impl.JDBCRepoService.query(JDBCRepoService.java:707)
      at org.forgerock.openidm.config.persistence.RepoPersistenceManager$1.hasMoreElements(RepoPersistenceManager.java:270)
      at org.apache.felix.cm.impl.CachingPersistenceManagerProxy.getDictionaries(CachingPersistenceManagerProxy.java:106)
      at org.apache.felix.cm.impl.ConfigurationManager.listConfigurations(ConfigurationManager.java:659)
      at org.apache.felix.cm.impl.ConfigurationAdminImpl.listConfigurations(ConfigurationAdminImpl.java:184)
      at org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.findConfigurations(ConfigurationComponentRegistry.java:357)
      at org.apache.felix.scr.impl.config.ConfigurationComponentRegistry.serviceChanged(ConfigurationComponentRegistry.java:183)
      at org.apache.felix.framework.util.EventDispatcher.invokeServiceListenerCallback(EventDispatcher.java:932)
      at org.apache.felix.framework.util.EventDispatcher.fireEventImmediately(EventDispatcher.java:793)
      at org.apache.felix.framework.util.EventDispatcher.fireServiceEvent(EventDispatcher.java:543)
      at org.apache.felix.framework.Felix.fireServiceEvent(Felix.java:4419)
      at org.apache.felix.framework.Felix.registerService(Felix.java:3423)
      at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:346)
      at org.apache.felix.framework.BundleContextImpl.registerService(BundleContextImpl.java:320)
      at org.apache.felix.cm.impl.ConfigurationManager.start(ConfigurationManager.java:284)
      at org.apache.felix.framework.util.SecureAction.startActivator(SecureAction.java:645)
      at org.apache.felix.framework.Felix.activateBundle(Felix.java:2146)
      at org.apache.felix.framework.Felix.startBundle(Felix.java:2064)
      at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1291)
      at org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
      at java.lang.Thread.run(Thread.java:745)

      Note: Tried to run some queries w/o IDM, the queries were fine, either w/ or w/o results but returned properly. One query select * from internaluser; returned results properly.
      The server was functional, as the same test with 5.0.0 was fine.

      To reproduce using Pyforge 4.5.0 branch: Put IDM 4.5.1 build under pyforge archives/, make necessary config changes and run the following command:
      COMMAND_LINE_ARGUMENTS="--variable OPENDJ_ZIP_PATH:/home/oracle/Downloads/OpenDJ-3.0.0.zip --variable REPO:oracle -e gui -e meta -e icf --exclude mysql_only --exclude orientdb_only --exclude windows_only"
      python -u run-pybot.py $COMMAND_LINE_ARGUMENTS -s info_service -t info_service_ping OpenIDM

        Attachments

          Activity

            People

            Assignee:
            cgdrake Chris Drake
            Reporter:
            Tinghua.Xu Tinghua Xu
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: