javax.naming.CommunicationException

Request: 2cancelled;

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web33

  • via Oracle Community by 807573, 1 year ago
    Request: 2cancelled;
  • Request: 1cancelled
  • via Oracle Community by 807573, 11 months ago
    Request: 1cancelled
  • Stack trace

    • javax.naming.CommunicationException: Request: 2cancelled; at com.sun.jndi.ldap.LdapRequest.getReplyBer(LdapRequest.java:47) at com.sun.jndi.ldap.Connection.readReply(Connection.java:275) at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:618) at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:534) at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1796) at com.sun.jndi.ldap.LdapCtx.searchAux(LdapCtx.java:1658) at com.sun.jndi.ldap.LdapCtx.c_search(LdapCtx.java:1583) at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(ComponentDirContext.java:371) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:331) at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(PartialCompositeDirContext.java:316) at javax.naming.directory.InitialDirContext.search(InitialDirContext.java:241)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago