Community resources
Community resources
Community resources
BadLdapGrammarException
Hi,
I have LDAP (AD) read-only with local groups configuration. All seems to be work fine, but synch with AD fails at the end. Seems that there were similar issues already (https://jira.atlassian.com/browse/CWD-183) but they were solved in 2008 ...
2013-02-20 14:24:35,998 QuartzWorker-1 INFO atlassian.crowd.directory.DbCachingRemoteChangeOperations scanning 17544 users to add or update
2013-02-20 14:24:36,000 QuartzWorker-1 INFO atlassian.crowd.directory.DbCachingRemoteChangeOperations scanned 00.0% users
2013-02-20 14:24:36,005 QuartzWorker-1 INFO atlassian.crowd.directory.DbCachingRemoteChangeOperations scanned 07.4% users
2013-02-20 14:24:36,019 QuartzWorker-1 INFO atlassian.crowd.directory.DbCachingRemoteChangeOperations scanned 24.5% users
2013-02-20 14:24:36,029 QuartzWorker-1 INFO atlassian.crowd.directory.DbCachingRemoteChangeOperations scanned 43.9% users
2013-02-20 14:24:36,087 QuartzWorker-1 INFO atlassian.crowd.directory.DbCachingRemoteChangeOperations scanned 93.5% users
2013-02-20 14:24:36,089 QuartzWorker-1 INFO atlassian.crowd.directory.DbCachingRemoteChangeOperations scanned 99.7% users
2013-02-20 14:24:36,089 QuartzWorker-1 INFO atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations scanned and compared 17544 users for update in DB cache in 1016ms
2013-02-20 14:24:36,089 QuartzWorker-1 INFO atlassian.crowd.directory.DirectoryCacheImplUsingChangeOperations synchronised 17544 users in 1016ms
2013-02-20 14:24:36,612 QuartzWorker-1 INFO atlassian.crowd.directory.DbCachingRemoteChangeOperations scanned and compared 17544 users for delete in DB cache in 522ms
2013-02-20 14:24:36,612 QuartzWorker-1 INFO atlassian.crowd.directory.DbCachingRemoteChangeOperations scanned for deleted users in 523ms
2013-02-20 14:24:36,613 QuartzWorker-1 INFO atlassian.crowd.directory.DbCachingRemoteDirectory failed synchronisation complete in 217287ms
2013-02-20 14:24:36,661 QuartzWorker-1 ERROR atlassian.crowd.directory.DbCachingDirectoryPoller Error occurred while refreshing the cache for directory 10001 .
com.atlassian.crowd.exception.OperationFailedException: java.util.concurrent.ExecutionException: com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: problem generating object using object factory Root exception is org.springframework.ldap.BadLdapGrammarException: Failed to parse DN; nested exception is org.springframework.ldap.core.TokenMgrError: Lexical error at line 1, column 27. Encountered: (92), after : ; remaining name 'OU=Company,DC=slf,DC=company,DC=net'
at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseAllGroups(UsnChangedCacheRefresher.java:299)
at com.atlassian.crowd.directory.ldap.cache.AbstractCacheRefresher.synchroniseAll(AbstractCacheRefresher.java:42)
at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseAll(UsnChangedCacheRefresher.java:223)
at com.atlassian.crowd.directory.DbCachingRemoteDirectory.synchroniseCache(DbCachingRemoteDirectory.java:619)
at com.atlassian.crowd.manager.directory.DirectorySynchroniserImpl.synchronise(DirectorySynchroniserImpl.java:63)
at com.atlassian.crowd.directory.DbCachingDirectoryPoller.pollChanges(DbCachingDirectoryPoller.java:50)
at com.atlassian.crowd.manager.directory.monitor.poller.DirectoryPollerJob.execute(DirectoryPollerJob.java:34)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: java.util.concurrent.ExecutionException: com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: problem generating object using object factory Root exception is org.springframework.ldap.BadLdapGrammarException: Failed to parse DN; nested exception is org.springframework.ldap.core.TokenMgrError: Lexical error at line 1, column 27. Encountered: (92), after : ; remaining name 'OU=Company,DC=slf,DC=Company,DC=net'
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher.synchroniseAllGroups(UsnChangedCacheRefresher.java:280)
... 9 more
Caused by: com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: problem generating object using object factory Root exception is org.springframework.ldap.BadLdapGrammarException: Failed to parse DN; nested exception is org.springframework.ldap.core.TokenMgrError: Lexical error at line 1, column 27. Encountered: (92), after : ; remaining name 'OU=Company,DC=slf,DC=Company,DC=net'
at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntitiesWithRequestControls(SpringLDAPConnector.java:399)
at com.atlassian.crowd.directory.SpringLDAPConnector.searchEntities(SpringLDAPConnector.java:384)
at com.atlassian.crowd.directory.SpringLDAPConnector.searchGroupObjectsOfSpecifiedGroupType(SpringLDAPConnector.java:1079)
at com.atlassian.crowd.directory.SpringLDAPConnector.searchGroupObjects(SpringLDAPConnector.java:1127)
at com.atlassian.crowd.directory.SpringLDAPConnector.searchGroups(SpringLDAPConnector.java:1136)
at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher$2.call(UsnChangedCacheRefresher.java:194)
at com.atlassian.crowd.directory.ldap.cache.UsnChangedCacheRefresher$2.call(UsnChangedCacheRefresher.java:189)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Caused by: org.springframework.ldap.UncategorizedLdapException: Uncategorized exception occured during LDAP processing; nested exception is javax.naming.NamingException: problem generating object using object factory Root exception is org.springframework.ldap.BadLdapGrammarException: Failed to parse DN; nested exception is org.springframework.ldap.core.TokenMgrError: Lexical error at line 1, column 27. Encountered: (92), after : ; remaining name 'OU=Company,DC=slf,DC=Company,DC=net'
at org.springframework.ldap.support.LdapUtils.convertLdapException(LdapUtils.java:215)
at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:319)
at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:237)
at com.atlassian.crowd.directory.ldap.LdapTemplateWithClassLoaderWrapper$4.call(LdapTemplateWithClassLoaderWrapper.java:88)
at com.atlassian.crowd.directory.ldap.LdapTemplateWithClassLoaderWrapper$4.call(LdapTemplateWithClassLoaderWrapper.java:85)
at com.atlassian.crowd.directory.ldap.LdapTemplateWithClassLoaderWrapper.search(LdapTemplateWithClassLoaderWrapper.java:85)
at com.atlassian.crowd.directory.SpringLDAPConnector.pageSearchResults(SpringLDAPConnector.java:333)
... 12 more
Caused by: javax.naming.NamingException: problem generating object using object factory Root exception is org.springframework.ldap.BadLdapGrammarException: Failed to parse DN; nested exception is org.springframework.ldap.core.TokenMgrError: Lexical error at line 1, column 27. Encountered: (92), after : ; remaining name 'OU=Company,DC=slf,DC=Company,DC=net'
at com.sun.jndi.ldap.LdapSearchEnumeration.createItem(LdapSearchEnumeration.java:111)
at com.sun.jndi.ldap.LdapNamingEnumeration.nextAux(LdapNamingEnumeration.java:256)
at com.sun.jndi.ldap.LdapNamingEnumeration.nextImpl(LdapNamingEnumeration.java:236)
at com.sun.jndi.ldap.LdapNamingEnumeration.next(LdapNamingEnumeration.java:184)
at org.springframework.ldap.core.LdapTemplate.search(LdapTemplate.java:296)
Caused by: org.springframework.ldap.BadLdapGrammarException: Failed to parse DN; nested exception is org.springframework.ldap.core.TokenMgrError: Lexical error at line 1, column 27. Encountered: (92), after :
at org.springframework.ldap.core.DistinguishedName.parse(DistinguishedName.java:190)
at org.springframework.ldap.core.DistinguishedName.<init>(DistinguishedName.java:140)
at org.springframework.ldap.core.support.DefaultDirObjectFactory.constructAdapterFromName(DefaultDirObjectFactory.java:164)
at org.springframework.ldap.core.support.DefaultDirObjectFactory.getObjectInstance(DefaultDirObjectFactory.java:78)
at javax.naming.spi.DirectoryManager.createObjectFromFactories(DirectoryManager.java:218)
at com.sun.jndi.ldap.LdapSearchEnumeration.createItem(LdapSearchEnumeration.java:105)
... 22 more
Caused by: org.springframework.ldap.core.TokenMgrError: Lexical error at line 1, column 27. Encountered: (92), after :
at org.springframework.ldap.core.DnParserImplTokenManager.getNextToken(DnParserImplTokenManager.java:690)
at org.springframework.ldap.core.DnParserImpl.jj_ntk(DnParserImpl.java:249)
at org.springframework.ldap.core.DnParserImpl.attributeTypeAndValue(DnParserImpl.java:98)
at org.springframework.ldap.core.DnParserImpl.rdn(DnParserImpl.java:58)
at org.springframework.ldap.core.DnParserImpl.dn(DnParserImpl.java:23)
... 28 more
1 answer
Hi,
According to the following KB, this is caused by special characters (not necessarily slashes) in a child tree's name.
Please verify if there is any special characters on their names and try the synchronization again after removing the character.
If renaming is not possible, we will need to use filters in the User Directory configuration to not get that child tree.
Hope this helps,
Marcus
Hi Marcus,
thank you for help.
I think that my issue is related to link you sent. But there is one important information missing in the text : JIRA version affected.
Accordign to several references (https://jira.atlassian.com/browse/CWD-1152 and it's "blocker" CORE-100). This issue should not be my problem.
Anyway it is really unfortunate behaviour. I think that synchronization should continue and failed CN should be listed in the log ...
I'm trying to find out problematic CN record and then eliminate them.
Regards,
vlada
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.