org.codehaus.xfire.fault.XFireFault: Could not parse message.

Atlassian JIRA | Brian Youngstrom | 10 years 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

    [CWD-183] Problems with LDAP group or user names that contain / or \. - Atlassian JIRA

    atlassian.com | 11 months ago
    org.codehaus.xfire.fault.XFireFault: Could not parse message.
  2. 0

    The following LDAP exception occurs when reading in a group named {{!Website Feedback/Support}} from an Active Directory server: {noformat} org.springframework.ldap.UncategorizedLdapException: Operation failed; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 000020D6: SvcErr: DSID-031006CC, problem 5012 (DIR_ERROR), data 0 ]; remaining name 'cn=!Website Feedback/Support, ou=Distribution Lists, ou=Groups, dc=corp, dc=example, dc=com' javax.naming.NamingException: [LDAP: error code 1 - 000020D6: SvcErr: DSID-031006CC, problem 5012 (DIR_ERROR), data 0 ]; remaining name 'cn=!Website Feedback/Support, ou=Distribution Lists, ou=Groups, dc=corp, dc=example, dc=com' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3025) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2931) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2737) {noformat} This exception then propergates to the wire layer as an exception on the client: {noformat} org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Could not parse message. org.codehaus.xfire.fault.XFireFault: Could not parse message. at org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage(Soap11FaultSerializer.java:78) at org.codehaus.xfire.fault.SoapFaultSerializer.readMessage(SoapFaultSerializer.java:28) {noformat}

    Atlassian JIRA | 10 years ago | Brian Youngstrom
    org.codehaus.xfire.fault.XFireFault: Could not parse message.
  3. 0

    The following LDAP exception occurs when reading in a group named {{!Website Feedback/Support}} from an Active Directory server: {noformat} org.springframework.ldap.UncategorizedLdapException: Operation failed; nested exception is javax.naming.NamingException: [LDAP: error code 1 - 000020D6: SvcErr: DSID-031006CC, problem 5012 (DIR_ERROR), data 0 ]; remaining name 'cn=!Website Feedback/Support, ou=Distribution Lists, ou=Groups, dc=corp, dc=example, dc=com' javax.naming.NamingException: [LDAP: error code 1 - 000020D6: SvcErr: DSID-031006CC, problem 5012 (DIR_ERROR), data 0 ]; remaining name 'cn=!Website Feedback/Support, ou=Distribution Lists, ou=Groups, dc=corp, dc=example, dc=com' at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3025) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2931) at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2737) {noformat} This exception then propergates to the wire layer as an exception on the client: {noformat} org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: Could not parse message. org.codehaus.xfire.fault.XFireFault: Could not parse message. at org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage(Soap11FaultSerializer.java:78) at org.codehaus.xfire.fault.SoapFaultSerializer.readMessage(SoapFaultSerializer.java:28) {noformat}

    Atlassian JIRA | 10 years ago | Brian Youngstrom
    org.codehaus.xfire.fault.XFireFault: Could not parse message.
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. org.codehaus.xfire.fault.XFireFault

      Could not parse message.

      at org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage()
    2. XFire
      SoapFaultSerializer.readMessage
      1. org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage(Soap11FaultSerializer.java:78)
      2. org.codehaus.xfire.fault.SoapFaultSerializer.readMessage(SoapFaultSerializer.java:28)
      2 frames