Details
-
Bug
-
Resolution: Fixed
-
High
-
8.11.0, 8.11.1
-
8.11
-
3
-
Severity 2 - Major
-
7
-
Description
Issue Summary
Incremental synchronisation fails back to Full synchronisation with a SQL Exception only in Jira version 8.11.x versions in Postgres database
Steps to Reproduce
- Install Jira 8.11.x version
- Connect to AD (Tested with Microsoft AD windows with Postgres database)
- Perform a Synchronisation (⚙️> User Management > User Directories > Synchronise)
- Parallely check atlassian-jira.log
- Full synchronisation works as expected
- Hit the 'Synchronise' button right after a Full sync to force Jira perform an Incremental sync (OR wait for an auto Incremental sync)
- Check atlassian-jira.log
Expected Results
Incremental synchronisation should not fail back to Full synchronisation with a SQL Exception
Actual Results
The below exception is thrown in the atlassian-jira.log file: Complete Stack trace
2020-08-24 15:23:52,433+0530 Caesium-2-3 ERROR ServiceRunner [c.a.crowd.directory.DbCachingRemoteDirectory] Incremental synchronisation for directory [ 10000 ] was unexpectedly interrupted, falling back to a full synchronisation com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, group_name, lower_group_name, active, local, created_date, updated_date, description, lower_description, group_type, directory_id, external_id FROM public.cwd_group WHERE (directory_id=?) AND (local = ? ) (ERROR: operator does not exist: numeric = boolean Hint: No operator matches the given name and argument types. You might need to add explicit type casts. Position: 212) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findListIteratorByCondition(DefaultOfBizDelegator.java:408) at com.atlassian.jira.ofbiz.WrappingOfBizDelegator.findListIteratorByCondition(WrappingOfBizDelegator.java:283) at com.atlassian.jira.entity.SelectQueryImpl$ExecutionContextImpl.forEach(SelectQueryImpl.java:227) at com.atlassian.jira.crowd.embedded.ofbiz.OfBizGroupDao.getLocalGroupNames(OfBizGroupDao.java:348) at com.atlassian.crowd.directory.DbCachingRemoteChangeOperations.getAllLocalGroupNames(DbCachingRemoteChangeOperations.java:1350) at com.atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations.getAllLocalGroupNames(DirectoryCacheImplUsingChangeOperations.java:296)
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available