-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 6.5.0.2
-
Fix Version/s: None
-
Labels:
When enabling queued sync for a mapping, the mapping name is used to create a lock. This causes an SQL error when the mapping name is greater than 38 characters. This stops the sync queue consumer from starting up, and sync requests sit in the queue without being processed.
For example, when using a mapping name "managedUser_systemAmuserstoreAccount_entitlements", the following appears in the log (full stack trace in attachment):
FINE: Getting table handler for locks [12] Jan 14, 2020 11:35:29.839 PM org.postgresql.jdbc.PgConnection setAutoCommit FINE: setAutoCommit = false [12] Jan 14, 2020 11:35:29.840 PM org.forgerock.openidm.repo.jdbc.impl.ExplicitTableHandler create FINE: Create with fullid locks/managedUser_systemAmuserstoreAccount_entitlements [12] Jan 14, 2020 11:35:29.840 PM org.forgerock.openidm.repo.jdbc.impl.ExplicitTableHandler create FINE: Preparing statement org.forgerock.openidm.repo.jdbc.impl.query.TracedPreparedStatement@60b81757 with locks, managedUser_systemAmuserstoreAccount_entitlements, 0 [12] Jan 14, 2020 11:35:29.840 PM org.forgerock.openidm.repo.jdbc.impl.ExplicitTableHandler create FINE: Executing: org.forgerock.openidm.repo.jdbc.impl.query.TracedPreparedStatement@60b81757 [12] Jan 14, 2020 11:35:29.845 PM org.forgerock.openidm.repo.jdbc.impl.JDBCRepoService lambda$handleCreate$2 FINE: SQL Exception in create of locks/managedUser_systemAmuserstoreAccount_entitlements with error code 0, sql state 22001 org.postgresql.util.PSQLException: ERROR: value too long for type character varying(38)
- duplicates
-
-
- Closed
-