You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Tammo van Lessen (JIRA)" <ji...@apache.org> on 2010/04/13 14:29:27 UTC

[jira] Updated: (ODE-461) Axis generates incorrect SOAP faults with some ODE exceptions

     [ https://issues.apache.org/jira/browse/ODE-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tammo van Lessen updated ODE-461:
---------------------------------

    Fix Version/s: 1.3.5

> Axis generates incorrect SOAP faults with some ODE exceptions
> -------------------------------------------------------------
>
>                 Key: ODE-461
>                 URL: https://issues.apache.org/jira/browse/ODE-461
>             Project: ODE
>          Issue Type: Bug
>          Components: Axis2 Integration
>    Affects Versions: 1.2
>            Reporter: Alexey Ousov
>             Fix For: 1.3.5
>
>         Attachments: ODE-461.patch
>
>
> I don't know for whom to blame with this bug, but since it can be easilly fixed on ODE side, I report it here. In some cases, when internal error occur within ODE, it returns incorrect SOAP fault as following:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>   <soapenv:Body>
>     <soapenv:Fault xmlns:soapenv="http://incubator.apache.org/ode">
>       <faultcode>soapenv:Fault</faultcode>
>       <faultstring>Timeout or execution error when waiting for response to MEX {MyRoleMex#4611686018427387903 [Client hqejbhcnphr3tgmhuqms9i] calling {http://www.comped.it/STD_QDS_RSR68}STD_QDS_RSR68.STD_QDS_RSR68(...)} java.util.concurrent.TimeoutException: Message exchange org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture@71edc0 timed out when waiting for a response!</faultstring>
>       <detail/>
>     </soapenv:Fault>
>   </soapenv:Body>
> </soapenv:Envelope>
> You can notice, that this element <soapenv:Fault xmlns:soapenv="http://incubator.apache.org/ode"> and all its children have incorrect namespace, so automatic processing routines don't recognise fault here. This happens due to some code deeply in Axis2. This can be fixed with following patch, so fault envelope will look like this:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>   <soapenv:Body>
>     <soapenv:Fault xmlns:ode="http://incubator.apache.org/ode">
>       <faultcode>ode:Fault</faultcode>
>       <faultstring>Timeout or execution error when waiting for response to MEX {MyRoleMex#4611686018427387903 [Client hqejbhcnphr3tl71dm4x8g] calling {http://www.comped.it/STD_QDS_RSR}STD_QDS_RSR.STD_QDS_RSR(...)} java.util.concurrent.TimeoutException: Message exchange org.apache.ode.bpel.engine.MyRoleMessageExchangeImpl$ResponseFuture@1a63a1c timed out when waiting for a response!</faultstring>
>       <detail/>
>     </soapenv:Fault>
>   </soapenv:Body>
> </soapenv:Envelope>

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira