javax.naming.CommunicationException: Request: 4 cancelled; remaining name '<cut-off>'

Atlassian JIRA | Andrew Michalec | 1 decade ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    [JRA-5292] LDAP authentication fails for Lotus Domino - Atlassian JIRA

    atlassian.com | 1 year ago
    javax.naming.CommunicationException: Request: 4 cancelled; remaining name '<cut-off>'
  2. 0

    Cannot authenticate user in Lotus Domino server even LDAP browsers can (parameters validity checked). LDAP Configurator states: "Initial connect and search successful, but second phase connection to LDAP as '<cut-off>' failed (error: javax.naming.CommunicationException: Request: 4 cancelled; remaining name '<cut-off>'. More in logs)" Logs states: 2004-11-19 14:33:57,662 INFO [web.action.util.LDAPConfigurer] javax.naming.Commu nicationException: Request: 4 cancelled; remaining name '<cut-off>' javax.naming.CommunicationException: Request: 4 cancelled; remaining name '<cut-off>' at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:60) at com.sun.jndi.ldap.Connection.readReply(Connection.java:405) at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:340) at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:193) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2640) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2549) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2523) at com.sun.jndi.ldap.LdapCtx.compare(LdapCtx.java:2075) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1804) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1734) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirCon text.java:368) ... This is known Domino problem - two phase LDAP querying requires reconnecion (see: https://list.unm.edu/cgi-bin/wa?A2=ind0311&L=jasig-portal&F=&S=&P=21622) LDAP libraries could be LDAP-vendor sensible, provided third party library license allows it.

    Atlassian JIRA | 1 decade ago | Andrew Michalec
    javax.naming.CommunicationException: Request: 4 cancelled; remaining name '<cut-off>'
  3. 0

    Cannot authenticate user in Lotus Domino server even LDAP browsers can (parameters validity checked). LDAP Configurator states: "Initial connect and search successful, but second phase connection to LDAP as '<cut-off>' failed (error: javax.naming.CommunicationException: Request: 4 cancelled; remaining name '<cut-off>'. More in logs)" Logs states: 2004-11-19 14:33:57,662 INFO [web.action.util.LDAPConfigurer] javax.naming.Commu nicationException: Request: 4 cancelled; remaining name '<cut-off>' javax.naming.CommunicationException: Request: 4 cancelled; remaining name '<cut-off>' at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:60) at com.sun.jndi.ldap.Connection.readReply(Connection.java:405) at com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:340) at com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:193) at com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2640) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2549) at com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2523) at com.sun.jndi.ldap.LdapCtx.compare(LdapCtx.java:2075) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1804) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1734) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirCon text.java:368) ... This is known Domino problem - two phase LDAP querying requires reconnecion (see: https://list.unm.edu/cgi-bin/wa?A2=ind0311&L=jasig-portal&F=&S=&P=21622) LDAP libraries could be LDAP-vendor sensible, provided third party library license allows it.

    Atlassian JIRA | 1 decade ago | Andrew Michalec
    javax.naming.CommunicationException: Request: 4 cancelled; remaining name '<cut-off>'
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    IBM LDAPSYNC Error: Connection reset - United States

    ibm.com | 8 months ago
    javax.naming.CommunicationException: Connection reset [Root exception is java.net.SocketException: Connection reset]; remaining name 'dc=ibm,dc=com'
  6. 0

    Detect and handle LDAP context closure

    Oracle Community | 1 decade ago | 843793
    javax.naming.CommunicationException: connection closed. Root exception is java.io.IOException: connection closed

    Root Cause Analysis

    1. javax.naming.CommunicationException

      Request: 4 cancelled; remaining name '<cut-off>'

      at com.sun.jndi.ldap.LdapRequest.getReplyBer()
    2. Java RT
      LdapCtx.c_search
      1. com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:60)
      2. com.sun.jndi.ldap.Connection.readReply(Connection.java:405)
      3. com.sun.jndi.ldap.LdapClient.ldapBind(LdapClient.java:340)
      4. com.sun.jndi.ldap.LdapClient.authenticate(LdapClient.java:193)
      5. com.sun.jndi.ldap.LdapCtx.connect(LdapCtx.java:2640)
      6. com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2549)
      7. com.sun.jndi.ldap.LdapCtx.ensureOpen(LdapCtx.java:2523)
      8. com.sun.jndi.ldap.LdapCtx.compare(LdapCtx.java:2075)
      9. com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1804)
      10. com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1734)
      10 frames