LDAP sync repeats the same user and sync group membership throws an error in catalina.out

  • 7014336
  • 19-Dec-2013
  • 20-Feb-2015

Environment

Novell Vibe 3.4

Situation

After upgrading to Vibe 3.4, the LDAP sync process may continue to repeat the same user on every LDAP sync. If synchronize group membership is checked, it may appear that the LDAP sync process never completes.

An additional symptom of this error is that the LDAP configuration page may loose the previously defined LDAP schedule and/or the other checkbox options under User and Group synchronization sections.

Resolution

A fix for this issue is available in the Vibe 3.4 Hot Patch 1, available via the Novell Patch Finder.

Additional Information

The following error condition was observed in catalina.out:

org.kablink.teaming.domain.NoUserByTheIdException: No such user by the id '553,681'
    at org.kablink.teaming.dao.impl.ProfileDaoImpl.loadUser(ProfileDaoImpl.java:905)
    at org.kablink.teaming.module.profile.impl.ProfileModuleImpl.getUser(ProfileModuleImpl.java:391)
    at org.kablink.teaming.module.profile.impl.ProfileModuleImpl.getUserProperties(ProfileModuleImpl.java:549)
    at org.kablink.teaming.module.profile.impl.ProfileModuleImpl.isUserExternal(ProfileModuleImpl.java:2095)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:309)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
    at org.kablink.teaming.search.interceptor.IndexSynchronizationManagerInterceptor.invoke(IndexSynchronizationManagerInterceptor.java:67)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
    at org.kablink.teaming.module.interceptor.EventListenerManagerInterceptor.invoke(EventListenerManagerInterceptor.java:64)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
    at org.kablink.teaming.util.aopalliance.InvocationStatisticsInterceptor.invoke(InvocationStatisticsInterceptor.java:49)
    at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
    at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
    at $Proxy18.isUserExternal(Unknown Source)
    at org.kablink.teaming.module.shared.EntityIndexUtils.addEntryType(EntityIndexUtils.java:308)
    at org.kablink.teaming.module.binder.impl.AbstractEntryProcessor.fillInIndexDocWithCommonPartFromEntry(AbstractEntryProcessor.java:1535)
    at org.kablink.teaming.module.binder.impl.AbstractEntryProcessor.buildIndexDocumentFromEntry(AbstractEntryProcessor.java:1485)
    at org.kablink.teaming.module.profile.impl.DefaultProfileCoreProcessor.buildIndexDocumentFromEntry(DefaultProfileCoreProcessor.java:560)
    at org.kablink.teaming.module.binder.impl.AbstractEntryProcessor.indexEntryWithAttachments(AbstractEntryProcessor.java:1463)
    at org.kablink.teaming.module.binder.impl.AbstractEntryProcessor.indexEntry(AbstractEntryProcessor.java:1430)
    at org.kablink.teaming.module.binder.impl.AbstractEntryProcessor.indexEntry(AbstractEntryProcessor.java:1401)
    at org.kablink.teaming.module.binder.impl.AbstractEntryProcessor.indexEntries(AbstractEntryProcessor.java:1265)
    at org.kablink.teaming.module.profile.impl.ProfileModuleImpl.indexEntries(ProfileModuleImpl.java:1019)
    at sun.reflect.GeneratedMethodAccessor611.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    .............................

Feedback service temporarily unavailable. For content questions or problems, please contact Support.