org.jdom.IllegalDataException

The data "Operation failed; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece^@]" is not legal for a JDOM character content: 0x0 is not a legal XML character.

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 web49

  • The data "Operation failed; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece^@]" is not legal for a JDOM character content: 0x0 is not a legal XML character.
  • The data "Operation failed; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece^@]" is not legal for a JDOM character content: 0x0 is not a legal XML character.
  • via Atlassian JIRA by Justen Stepka [Atlassian], 11 months ago
    The data "Operation failed; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 532, vece^@]" is not legal for a JDOM character content: 0x0 is not a legal XML character.
  • Stack trace

    • org.jdom.IllegalDataException: The data "Operation failed; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece^@]" is not legal for a JDOM character content: 0x0 is not a legal XML character. at org.jdom.Text.setText(Text.java:188) at org.jdom.Text.<init>(Text.java:99) at org.jdom.Element.addContent(Element.java:799) at org.codehaus.xfire.util.stax.JDOMStreamWriter.writeCharacters(JDOMStreamWriter.java:208)

    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

    You’re the first here who have seen this exception.