LDAP Transform Histories in "Running" state and corresponding Importsets in "Cancelled" stateDescriptionLDAP Transform Histories in "Running" state and corresponding Import sets in "Cancelled" state. Confirm that the LDAP listener is enabled. The imporsets have the short description "Import from ldap listener or ldap authentication ....." Enable the property glide.ldap.debug and set it to true. Go through the application nodes and run threads.do Identify the node running the thread "glide.ldap.listener-<LDAP_server_sys_id>". In the same node you will be able to track the thread "LDAP Transform<LDAP_server_sys_id>". From the thread "LDAP Transform<LDAP_server_sys_id>" there will be a stack trace more or less similar to the one below. This confirms that the instance has established connection to the LDAP server. java.net.SocketInputStream.socketRead0(Native Method)java.net.SocketInputStream.socketRead(SocketInputStream.java:116)java.net.SocketInputStream.read(SocketInputStream.java:171)java.net.SocketInputStream.read(SocketInputStream.java:141)sun.security.ssl.InputRecord.readFully(InputRecord.java:465)sun.security.ssl.InputRecord.read(InputRecord.java:503)sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:975)sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1367)sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1395)sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1379)com.sun.jndi.ldap.Connection.createSocket(Connection.java:393)com.sun.jndi.ldap.Connection.(Connection.java:215)com.sun.jndi.ldap.LdapClient.(LdapClient.java:137)com.sun.jndi.ldap.LdapClient.getInstance(LdapClient.java:1609)com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2749)com.sun.jndi.ldap.LdapCtx.(LdapCtx.java:319)com.sun.jndi.ldap.LdapCtxFactory.getUsingURL(LdapCtxFactory.java:192)com.sun.jndi.ldap.LdapCtxFactory.getUsingURLs(LdapCtxFactory.java:210)com.sun.jndi.ldap.LdapCtxFactory.getLdapCtxInstance(LdapCtxFactory.java:153)com.sun.jndi.ldap.LdapCtxFactory.getInitialContext(LdapCtxFactory.java:83)javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313)javax.naming.InitialContext.init(InitialContext.java:244)javax.naming.InitialContext.(InitialContext.java:216)javax.naming.directory.InitialDirContext.(InitialDirContext.java:101)com.glide.sys.ldap.AbstractLDAP.getLDAPRecord(AbstractLDAP.java:169)com.glide.sys.ldap.AbstractLDAPTarget.nextListenerRecord(AbstractLDAPTarget.java:169)com.glide.sys.ldap.AbstractLDAPTarget.next(AbstractLDAPTarget.java:145) In the logs you will get an error similar to what we have below when the LDAP transformation is being canceled after 10 minutes by glide.quota.manager. 2020-03-11 06:34:52 (062) LDAP Transform<LDAP_server_sys_id> SYSTEM txid=2459be60db67 WARNING *** WARNING *** LDAP API - LDAPLogger : Interrupted during LDAP operation:Interrupted during LDAP operation2020-03-11 06:34:52 (062) glide.quota.manager SYSTEM Cancelled 0 child transactions2020-03-11 06:34:52 (062) LDAP Transform<LDAP_server_sys_id> SYSTEM txid=2459be60db67 WARNING *** WARNING *** Long Transaction started at 03/11/20 06:24:51.987, Memory at start was 342, Memory is 463, SQL count is 169, BR count is now 1.2020-03-11 06:34:52 (062) LDAP Transform<LDAP_server_sys_id> SYSTEM txid=2459be60db67 WARNING *** WARNING *** Transaction cancelled: maximum execution time exceeded2020-03-11 06:34:52 (211) LDAP Transform<LDAP_server_sys_id> SYSTEM txid=2459be60db67 WARNING *** WARNING *** LDAP listen transform thread caught TransactionCancelledException Transaction cancelled: maximum execution time exceeded CauseThis is expected behavior since the conditions of this transactions are triggering the quota rule. The LDAP transform transaction is cancelled by the quota rule "LDAP Listener Transform Transaction" There are large number of records pending on the LDAP server to be processed by the listener.ResolutionYou can carry out one of the options below.1. Carry out optimization on the LDAP server to increase the number of records being processed per second.2. Try setting the system property glide.ldap.listener.transform.use_background_transaction to false. However not that the consequence of this action is that the transactions might wait indefinitely.3. If the LAP server cannot process records faster than the current rate then disable the listener for this particular LDAP server.