Rampart
  1. Rampart
  2. RAMPART-164

Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 1.4
    • Fix Version/s: None
    • Component/s: rampart-core
    • Labels:
      None

      Description

      Rampart throws an Exception. A SOAP-Fault is generated and will be send to the caller. This SOAP-Fault is also Processed by Rampart and while processing this Fault Message, Rampart throws another Error that causes Axis2 to send an HTML-internal error message to the caller.

      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing"><wsa:Action>XXXXXXXXX/Fault/FaultName</wsa:Action><wsa:RelatesTo>urn:uuid:E4331B281C8C1BE1411210178240805</wsa:RelatesTo></soapenv:Header><soapenv:Body><soapenv:Fault xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><faultcode>wsse:InvalidSecurity</faultcode><faultstring>Cannot load password callback class: xxx.xxx.xxx.PWCBHandler.java</faultstring><detail /></soapenv:Fault></soapenv:Body></soapenv:Envelope>

      2008-01-31 23:37:05,844 [http-8080-Processor15] DEBUG org.apache.axis2.engine.Phase - [MessageContext: logID=urn:uuid:AEE3166C73B98914F81201818949494] Invoking Handler 'Apache Rampart outflow handler' in Phase 'Security'

      org.apache.ws.security.WSSecurityException: Error in converting SOAP Envelope to Document; nested exception is:
      org.apache.axiom.soap.SOAPProcessingException: Only Characters are allowed here

      in Axis2Util.getDocumentFromSOAPEnveloper

      This Exception does not make the way through Axis engine..... somehow the following exception pops up at Axis2Servlet

      "org.apache.axis2.AxisFault: Error in extracting message properties"

        Issue Links

          Activity

          Hide
          Stefan Lischke added a comment -

          This happens on all AxisFaults not only the ones that occur in Rampart Processing.

          Its caused by Line 134 of Axis2Util

          ((OMNode) envelope.getParent()).build();

          org.apache.axiom.soap.SOAPProcessingException: Only Characters are allowed here

          Show
          Stefan Lischke added a comment - This happens on all AxisFaults not only the ones that occur in Rampart Processing. Its caused by Line 134 of Axis2Util ((OMNode) envelope.getParent()).build(); org.apache.axiom.soap.SOAPProcessingException: Only Characters are allowed here
          Hide
          Nandana Mihindukulasooriya added a comment -

          This is due to issue in AXIOM. Unfortunately we weren't able to get this fixed in AXIOM.

          http://markmail.org/message/ia57gpstcdzmc46w?q=list:org%2Eapache%2Ews%2Erampart-dev+AXIOM

          Show
          Nandana Mihindukulasooriya added a comment - This is due to issue in AXIOM. Unfortunately we weren't able to get this fixed in AXIOM. http://markmail.org/message/ia57gpstcdzmc46w?q=list:org%2Eapache%2Ews%2Erampart-dev+AXIOM
          Hide
          Stefan Lischke added a comment -

          Thanks!

          It works with SOAP 1.2

          But this issue is definitely for the Rampart Frontpage

          "Rampart does only work with SOAP 1.2 Binding (because of AXIOM)!"

          I searched a JIRA for this at wscommons but did not found anything? Isn't this issue filed?

          Show
          Stefan Lischke added a comment - Thanks! It works with SOAP 1.2 But this issue is definitely for the Rampart Frontpage "Rampart does only work with SOAP 1.2 Binding (because of AXIOM)!" I searched a JIRA for this at wscommons but did not found anything? Isn't this issue filed?
          Hide
          Nandana Mihindukulasooriya added a comment -

          Stefan,
          Yes, I agree. But the only possible solution for us at the moment as it seems is to list this as an known issue in Release as AXIOM has been already released. I will create a JIRA for this in the AXIOM project.

          thanks,
          nandana

          Show
          Nandana Mihindukulasooriya added a comment - Stefan, Yes, I agree. But the only possible solution for us at the moment as it seems is to list this as an known issue in Release as AXIOM has been already released. I will create a JIRA for this in the AXIOM project. thanks, nandana
          Hide
          Nandana Mihindukulasooriya added a comment -

          Create an issue in WSCOMMONS/AXIOM.

          https://issues.apache.org/jira/browse/WSCOMMONS-343

          Show
          Nandana Mihindukulasooriya added a comment - Create an issue in WSCOMMONS/AXIOM. https://issues.apache.org/jira/browse/WSCOMMONS-343
          Hide
          chris grzegorczyk added a comment -

          Hi Folks,

          I've been following this problem for a little while now. Has there been any change in the situation? I notice that the AXIOM bug is as yet unassigned – is that a sign the issue will not be addressed?

          Is there possibly a short-term work around?

          Using SOAP 1.2 is not an option for me.

          thanks in advance.

          Show
          chris grzegorczyk added a comment - Hi Folks, I've been following this problem for a little while now. Has there been any change in the situation? I notice that the AXIOM bug is as yet unassigned – is that a sign the issue will not be addressed? Is there possibly a short-term work around? Using SOAP 1.2 is not an option for me. thanks in advance.
          Show
          Nandana Mihindukulasooriya added a comment - Fixed with the issue https://issues.apache.org/jira/browse/WSCOMMONS-343 .
          Hide
          Nikolaus Krismer added a comment -

          Will there be any "hotfix-release" for Rampart-1.4, now that the fix is available?

          Show
          Nikolaus Krismer added a comment - Will there be any "hotfix-release" for Rampart-1.4, now that the fix is available?
          Hide
          Nandana Mihindukulasooriya added a comment -

          Hi Nikolaus,
          The problem is "hotfix-release" will have to happen in AXIOM and not in Rampart. This was an AXIOM issue rather than a Rampart issue. You can try convincing AXIOM folks for a release .

          thanks,
          nandana

          Show
          Nandana Mihindukulasooriya added a comment - Hi Nikolaus, The problem is "hotfix-release" will have to happen in AXIOM and not in Rampart. This was an AXIOM issue rather than a Rampart issue. You can try convincing AXIOM folks for a release . thanks, nandana
          Hide
          Chris Emerson added a comment -

          I am running into the same issue as Matthias except that i have Axis2 1.5 which already has the axiom 1.2.8 jars. Am I missing something else in the fix?

          Show
          Chris Emerson added a comment - I am running into the same issue as Matthias except that i have Axis2 1.5 which already has the axiom 1.2.8 jars. Am I missing something else in the fix?

            People

            • Assignee:
              Nandana Mihindukulasooriya
              Reporter:
              Stefan Lischke
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development