You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Jason Walton (JIRA)" <ji...@apache.org> on 2008/09/11 21:57:44 UTC

[jira] Created: (SYNAPSE-444) Failures in SALoadBalanceEndpoint result in "empty" faults back to the client.

Failures in SALoadBalanceEndpoint result in "empty" faults back to the client.
------------------------------------------------------------------------------

                 Key: SYNAPSE-444
                 URL: https://issues.apache.org/jira/browse/SYNAPSE-444
             Project: Synapse
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.1, 1.2, 1.3
            Reporter: Jason Walton
            Priority: Minor


In failure cases in SALoadBalanceEndpoint, we call into informFailure(), which in turn calls into "handleFault()" on the top handler of the fault stack.  The call to handleFault(), however, does not supply an exception or a fault message, so the fault received by the client looks something like this:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Header></soapenv:Header>
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
         <faultstring/>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>

Since it took me forever to figure out where these faults were coming from, it would be nice if we returned something a touch more descriptive.  :)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


[jira] Resolved: (SYNAPSE-444) Failures in SALoadBalanceEndpoint result in "empty" faults back to the client.

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

Ruwan Linton resolved SYNAPSE-444.
----------------------------------

       Resolution: Fixed
    Fix Version/s: NIGHTLY

Fixed on the trunk

> Failures in SALoadBalanceEndpoint result in "empty" faults back to the client.
> ------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-444
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-444
>             Project: Synapse
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1, 1.2, 1.3
>            Reporter: Jason Walton
>            Assignee: Ruwan Linton
>            Priority: Minor
>             Fix For: NIGHTLY
>
>
> In failure cases in SALoadBalanceEndpoint, we call into informFailure(), which in turn calls into "handleFault()" on the top handler of the fault stack.  The call to handleFault(), however, does not supply an exception or a fault message, so the fault received by the client looks something like this:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>    <soapenv:Header></soapenv:Header>
>    <soapenv:Body>
>       <soapenv:Fault>
>          <faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
>          <faultstring/>
>       </soapenv:Fault>
>    </soapenv:Body>
> </soapenv:Envelope>
> Since it took me forever to figure out where these faults were coming from, it would be nice if we returned something a touch more descriptive.  :)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


[jira] Commented: (SYNAPSE-444) Failures in SALoadBalanceEndpoint result in "empty" faults back to the client.

Posted by "Jason Walton (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SYNAPSE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630585#action_12630585 ] 

Jason Walton commented on SYNAPSE-444:
--------------------------------------

Actually, one minor exception; in onChildEndpointFail(), where we call informFailure() because of an error from the child endpoint, we don't want to explicitly set the exception, since we already have a nice fault message from the destination webservice.

> Failures in SALoadBalanceEndpoint result in "empty" faults back to the client.
> ------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-444
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-444
>             Project: Synapse
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1, 1.2, 1.3
>            Reporter: Jason Walton
>            Priority: Minor
>
> In failure cases in SALoadBalanceEndpoint, we call into informFailure(), which in turn calls into "handleFault()" on the top handler of the fault stack.  The call to handleFault(), however, does not supply an exception or a fault message, so the fault received by the client looks something like this:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>    <soapenv:Header></soapenv:Header>
>    <soapenv:Body>
>       <soapenv:Fault>
>          <faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
>          <faultstring/>
>       </soapenv:Fault>
>    </soapenv:Body>
> </soapenv:Envelope>
> Since it took me forever to figure out where these faults were coming from, it would be nice if we returned something a touch more descriptive.  :)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


[jira] Commented: (SYNAPSE-444) Failures in SALoadBalanceEndpoint result in "empty" faults back to the client.

Posted by "Ruwan Linton (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/SYNAPSE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642063#action_12642063 ] 

Ruwan Linton commented on SYNAPSE-444:
--------------------------------------

This should now be fixed on the trunk. Any way for the SAL endpoint does not handle faults coming from the server, if a SOAPFault is coming from the web service and is not being propagated to the client.... this should be a configuration error.

> Failures in SALoadBalanceEndpoint result in "empty" faults back to the client.
> ------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-444
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-444
>             Project: Synapse
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1, 1.2, 1.3
>            Reporter: Jason Walton
>            Assignee: Ruwan Linton
>            Priority: Minor
>
> In failure cases in SALoadBalanceEndpoint, we call into informFailure(), which in turn calls into "handleFault()" on the top handler of the fault stack.  The call to handleFault(), however, does not supply an exception or a fault message, so the fault received by the client looks something like this:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>    <soapenv:Header></soapenv:Header>
>    <soapenv:Body>
>       <soapenv:Fault>
>          <faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
>          <faultstring/>
>       </soapenv:Fault>
>    </soapenv:Body>
> </soapenv:Envelope>
> Since it took me forever to figure out where these faults were coming from, it would be nice if we returned something a touch more descriptive.  :)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


[jira] Assigned: (SYNAPSE-444) Failures in SALoadBalanceEndpoint result in "empty" faults back to the client.

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

Ruwan Linton reassigned SYNAPSE-444:
------------------------------------

    Assignee: Ruwan Linton

> Failures in SALoadBalanceEndpoint result in "empty" faults back to the client.
> ------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-444
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-444
>             Project: Synapse
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1, 1.2, 1.3
>            Reporter: Jason Walton
>            Assignee: Ruwan Linton
>            Priority: Minor
>
> In failure cases in SALoadBalanceEndpoint, we call into informFailure(), which in turn calls into "handleFault()" on the top handler of the fault stack.  The call to handleFault(), however, does not supply an exception or a fault message, so the fault received by the client looks something like this:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>    <soapenv:Header></soapenv:Header>
>    <soapenv:Body>
>       <soapenv:Fault>
>          <faultcode xmlns:tns="http://www.w3.org/2003/05/soap-envelope">tns:Receiver</faultcode>
>          <faultstring/>
>       </soapenv:Fault>
>    </soapenv:Body>
> </soapenv:Envelope>
> Since it took me forever to figure out where these faults were coming from, it would be nice if we returned something a touch more descriptive.  :)

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org