External user registration on very large Filr systems sometimes fail

  • 7023073
  • 08-Jun-2018
  • 21-Jun-2018


Micro Focus Filr 3.3


In some Filr deployments configured with MS-SQL as database and containing more than 10 million synchronized files across all Net Folders, the process to register an external user may fail prematurely due to long query times against the database. On such systems it was also observed that the appserver.log contained very frequent occurrence of Optimistic Locking failure messages, such as (note that this error is not indicative of the external user registration failure):

2018-01-25 14:15:39,020 ERROR [http-apr-8443-exec-262] [kablink] [org.kablink.teaming.module.profile.impl.DefaultProfileCoreProcessor] - (5) 'sync entry' failed due to optimistic locking failure - Aborting
org.springframework.orm.hibernate3.HibernateOptimisticLockingFailureException: Object of class [org.kablink.teaming.domain.User] with identifier [1730]: optimistic locking failed; nested exception is org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [org.kablink.teaming.domain.User#1730]
    at org.springframework.orm.hibernate3.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:683)
    at org.springframework.orm.hibernate3.HibernateTransactionManager.convertHibernateAccessException(HibernateTransactionManager.java:794)


A fix for this issue is available in the Filr 3.4 Update. With the fix in place, additional database indices are defined which will help significantly improve the query time during external user registration.