You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Stefan Lischke (JIRA)" <ji...@apache.org> on 2008/05/07 19:50:56 UTC

[jira] Created: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

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

                 Key: RAMPART-164
                 URL: https://issues.apache.org/jira/browse/RAMPART-164
             Project: Rampart
          Issue Type: Bug
          Components: rampart-core
    Affects Versions: 1.4
            Reporter: Stefan Lischke
            Assignee: Ruchith Udayanga Fernando
            Priority: Critical


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"



-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621685#action_12621685 ] 

Nandana Mihindukulasooriya commented on RAMPART-164:
----------------------------------------------------

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

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Chris Emerson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12749912#action_12749912 ] 

Chris Emerson commented on RAMPART-164:
---------------------------------------

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?

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12597829#action_12597829 ] 

Nandana Mihindukulasooriya commented on RAMPART-164:
----------------------------------------------------

Create an issue in WSCOMMONS/AXIOM.

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

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Matthias Hausherr (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matthias Hausherr updated RAMPART-164:
--------------------------------------

    Comment: was deleted

(was: Well, the issue should be fixed in Axiom 1.2.8 so I replaced the Axiom jars axiom-api-1.2.7.jar, axiom-dom-1.2.7.jar and axiom-impl-1.2.7.jar with the jars from Axiom 1.2.8. Still the problems remains the same. Was anybody able to solve this and how did you do it?)

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Stefan Lischke (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595158#action_12595158 ] 

Stefan Lischke commented on RAMPART-164:
----------------------------------------

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?

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Commented: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by Stefan Lischke <li...@googlemail.com>.
i commented on the ws-commons bug, i hope someone will read it!

stefan

chris grzegorczyk (JIRA) wrote:
>     [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607264#action_12607264 ] 
> 
> chris grzegorczyk commented on RAMPART-164:
> -------------------------------------------
> 
> 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.

[jira] Commented: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "chris grzegorczyk (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12607264#action_12607264 ] 

chris grzegorczyk commented on RAMPART-164:
-------------------------------------------

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.

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nandana Mihindukulasooriya reassigned RAMPART-164:
--------------------------------------------------

    Assignee: Nandana Mihindukulasooriya  (was: Ruchith Udayanga Fernando)

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Matthias Hausherr (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12745361#action_12745361 ] 

Matthias Hausherr commented on RAMPART-164:
-------------------------------------------

Well, the issue should be fixed in Axiom 1.2.8 so I replaced the Axiom jars axiom-api-1.2.7.jar, axiom-dom-1.2.7.jar and axiom-impl-1.2.7.jar with the jars from Axiom 1.2.8. Still the problems remains the same. Was anybody able to solve this and how did you do it?

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Stefan Lischke (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594996#action_12594996 ] 

Stefan Lischke commented on RAMPART-164:
----------------------------------------

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

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595471#action_12595471 ] 

Nandana Mihindukulasooriya commented on RAMPART-164:
----------------------------------------------------

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

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Nikolaus Krismer (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621487#action_12621487 ] 

Nikolaus Krismer commented on RAMPART-164:
------------------------------------------

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

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Re: [jira] Resolved: RAMPART-164 , RAMPART-178

Posted by Stefan Lischke <li...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks Nandana,

great work!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIa3e9bsixtqnWg1oRAjF7AJ9/l1eeEOsXFJvZFlR3uxZ5twP0eACdGMmx
8XRU88p49D/F1SYRCeeXFds=
=ZpFW
-----END PGP SIGNATURE-----

[jira] Resolved: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nandana Mihindukulasooriya resolved RAMPART-164.
------------------------------------------------

    Resolution: Fixed

Fixed with the issue https://issues.apache.org/jira/browse/WSCOMMONS-343. 

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Nandana Mihindukulasooriya
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (RAMPART-164) Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page

Posted by "Nandana Mihindukulasooriya (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/RAMPART-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12595153#action_12595153 ] 

Nandana Mihindukulasooriya commented on RAMPART-164:
----------------------------------------------------

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

> Error while processing SOAP-Fault (Axis2Util.getDocumentFromSOAPEnveloper) -> Axis2 HTML Error Page 
> ----------------------------------------------------------------------------------------------------
>
>                 Key: RAMPART-164
>                 URL: https://issues.apache.org/jira/browse/RAMPART-164
>             Project: Rampart
>          Issue Type: Bug
>          Components: rampart-core
>    Affects Versions: 1.4
>            Reporter: Stefan Lischke
>            Assignee: Ruchith Udayanga Fernando
>            Priority: Critical
>
> 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"

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.