[OPENIDM-7430] IDM 4.5.1 fails to start when Oracle or DB2 is used as repo Created: 16/Jan/17  Updated: 13/Apr/17  Resolved: 13/Apr/17

Status: Closed
Project: OpenIDM
Component/s: Module - Repository JDBC
Affects Version/s: OpenIDM 4.5.1
Fix Version/s: OpenIDM 4.5.1

Type: Bug Priority: Blocker
Reporter: Tinghua Xu Assignee: Chris Drake
Resolution: Fixed Votes: 0
Labels: not-for-release-notes, regression
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

IDM 4.5.1 build runs on a CentOS with Oracle DB and DB2 as repo.


Attachments: File openidm0.log.0     File openidm0.log.0    
Verified Version/s:

 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



 Comments   
Comment by Tinghua Xu [ 16/Jan/17 ]

See the same problem with DB2, attached IDM log file.

Comment by Tinghua Xu [ 16/Jan/17 ]

Something related OPENIDM-7040?

Comment by Chris Drake [ 23/Jan/17 ]

Tinghua Xu Yes, good catch. Backported OPENIDM-7040 to the 4.5.x sustaining branch.

Comment by Laurent Bristiel [X] (Inactive) [ 26/Jan/17 ]

checked OK in revision 309d917ffef of 4.5.x branch

Comment by Lana Frost [ 13/Apr/17 ]

Remove from release notes

Generated at Fri Mar 05 07:27:00 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.