Environment
Novell Filr 1.2
Situation
LDAP sync on systems with very large user/group sets sometimes fail with an java.lang.NullPointerException. The same problem may also affect administrative search re-indexing.
The following error stack sequence is observed in appserver.log file when this happens:
2015-10-13 16:59:53,342 ERROR [http-apr-8443-exec-49] [org.hibernate.LazyInitializationException] - could not initialize proxy - the owning Session was closed
org.hibernate.LazyInitializationException: could not initialize proxy - the owning Session was closed
....
2015-10-13 16:59:53,348 ERROR [http-apr-8443-exec-49] [org.kablink.teaming.module.ldap.impl.LdapModuleImpl] - Unknown exception: java.lang.NullPointerException
The following error stack sequence is observed in appserver.log file when this happens:
2015-10-13 16:59:53,342 ERROR [http-apr-8443-exec-49] [org.hibernate.LazyInitializationException] - could not initialize proxy - the owning Session was closed
org.hibernate.LazyInitializationException: could not initialize proxy - the owning Session was closed
....
2015-10-13 16:59:53,348 ERROR [http-apr-8443-exec-49] [org.kablink.teaming.module.ldap.impl.LdapModuleImpl] - Unknown exception: java.lang.NullPointerException
Resolution
A fix for this issue is available in the Filr 1.2 Hot Patch 5, available via the Novell Patch Finder.
Note: A fix for this issue is already available in the Filr 2.0 FCS release.
Note: A fix for this issue is already available in the Filr 2.0 FCS release.