Topic
  • 12 replies
  • Latest Post - ‏2014-12-18T09:20:11Z by HermannSW
dp_admin
dp_admin
23 Posts

Pinned topic Error with Multi-Way results actions

‏2011-09-21T22:21:37Z |
Hello,

I am using Multi-way results actions to send the requests to multiple ws-proxy's on the same device. I am getting connection failure error, but ws-proxy is receiving these requests and also sending valid responses.

So the problem is with multi way result actions.

this is how the destinations are set.

<results mode="require-all" multiple-outputs="true">
<url>http://wsproxy1/url</url>
<url>http://wsproxy2/url</url>
<url>http://wsproxy3/url</url>
</results>.

The errors are

17:13:57 mpgw error 4804273 e 0x00c3000f mpgw (Multiwaympgw): Invalid URL
17:13:57 multistep error 4804273 > 0x80c00009 mpgw (Multiwaympgw): request nfstest_rule_2 #2 results: 'generated from INPUT sent to var://context/uservars/resultURLs using HTTP method POST' failed: All results targets failed
17:13:57 multistep error 4804273 > 0x00c30016 mpgw (Multiwaympgw): External URL protocol Error
17:13:57 network info 4804273 0x80e0015b mpgw (Multiwaympgw): HTTP response code 500 for 'http://ip/errorTestRule'
17:13:57 multistep error 4804273 > 0x00c30016 mpgw (Multiwaympgw): External URL protocol Error
17:13:57 network info 4804273 0x80e0015b mpgw (Multiwaympgw): HTTP response code 500 for 'http://ip/errorTestRule'
17:13:57 multistep error 4804273 > 0x00c30016 mpgw (Multiwaympgw): External URL protocol Error
17:13:57 network info 4804273 0x80e0015b mpgw (Multiwaympgw): HTTP response code 500 for 'http://ip/errorTestRule'

I have followed the pdf to set up these.

Thanks...
Updated on 2011-09-24T00:04:39Z at 2011-09-24T00:04:39Z by HermannSW
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Error with Multi-Way results actions

    ‏2011-09-22T19:01:49Z  
    Have you tried using just a regular results action for one of the targets?

    Have you tried using the Send a Test Message on the troubleshooting panel?
  • dp_admin
    dp_admin
    23 Posts

    Re: Error with Multi-Way results actions

    ‏2011-09-23T16:43:14Z  
    Have you tried using just a regular results action for one of the targets?

    Have you tried using the Send a Test Message on the troubleshooting panel?
    Yes. I tried this and its working.

    As a matter of fact, even with the multi way results action also, the backend web service proxy is get the request, but mpgw is closing the connection.
  • HermannSW
    HermannSW
    4903 Posts

    Re: Error with Multi-Way results actions

    ‏2011-09-24T00:04:39Z  
    • dp_admin
    • ‏2011-09-23T16:43:14Z
    Yes. I tried this and its working.

    As a matter of fact, even with the multi way results action also, the backend web service proxy is get the request, but mpgw is closing the connection.
    May you attach a simplified config export demonstrating what you reported?

     
    Hermann<myXsltBlog/>
  • HYSP_Rachan_hegde
    HYSP_Rachan_hegde
    4 Posts

    Re: Error with Multi-Way results actions

    ‏2013-09-10T05:28:25Z  
    • HermannSW
    • ‏2011-09-24T00:04:39Z
    May you attach a simplified config export demonstrating what you reported?

     
    Hermann<myXsltBlog/>

    Hi Herman,

    I am facing some what similar problem. My setting is a WS-Proxy will be calling multiple mpgw which in turn talks to a back end system. I am using multiple-outputs option of results action and mode="attempt-all" . The setup works fine for success scenarios and i am getting proper responses. But if i have a validate action in the mpgw and validation fails, WS-Proxy errors out with error code 0x00c30016. Can you provide some insight on this as to why this is happening.

     

    Thanks

  • HermannSW
    HermannSW
    4903 Posts

    Re: Error with Multi-Way results actions

    ‏2013-09-10T07:56:53Z  

    Hi Herman,

    I am facing some what similar problem. My setting is a WS-Proxy will be calling multiple mpgw which in turn talks to a back end system. I am using multiple-outputs option of results action and mode="attempt-all" . The setup works fine for success scenarios and i am getting proper responses. But if i have a validate action in the mpgw and validation fails, WS-Proxy errors out with error code 0x00c30016. Can you provide some insight on this as to why this is happening.

     

    Thanks

    Hi Rachan,

    from "Administration->Debug->View List of Event Codes" in WebGUI:

    0x00c30016 multistep error External URL protocol Error

    Please check your URLs.


    Hermann.

  • HYSP_Rachan_hegde
    HYSP_Rachan_hegde
    4 Posts

    Re: Error with Multi-Way results actions

    ‏2013-09-11T07:41:36Z  
    • HermannSW
    • ‏2013-09-10T07:56:53Z

    Hi Rachan,

    from "Administration->Debug->View List of Event Codes" in WebGUI:

    0x00c30016 multistep error External URL protocol Error

    Please check your URLs.


    Hermann.

    Hi Hermann,

    URL used to call the mpgw is correct. I am saying this because when i am running a success scenario and the WSP is calling the mpgw its giving successful response. Only when i test a scenario which causes a dp:reject or a validation failure (validation action) in the mpgw the WSP errors out with  0x00c30016 - 

     External URL protocol Error

    An external URL being accessed via a results or fetch action could not be accessed due to a protocol response failure.

    Also when in debugged(probe) it, even in the negative scenario the message reaches the mpgw and it sends back the response to the calling service.

    Not able to make sense on this.

     

    Thanks

    Updated on 2013-09-11T07:48:10Z at 2013-09-11T07:48:10Z by HYSP_Rachan_hegde
  • Vijay97
    Vijay97
    52 Posts

    Re: Error with Multi-Way results actions

    ‏2014-12-17T14:19:46Z  

    Hi Hermann,

    URL used to call the mpgw is correct. I am saying this because when i am running a success scenario and the WSP is calling the mpgw its giving successful response. Only when i test a scenario which causes a dp:reject or a validation failure (validation action) in the mpgw the WSP errors out with  0x00c30016 - 

     External URL protocol Error

    An external URL being accessed via a results or fetch action could not be accessed due to a protocol response failure.

    Also when in debugged(probe) it, even in the negative scenario the message reaches the mpgw and it sends back the response to the calling service.

    Not able to make sense on this.

     

    Thanks

     

    I am facing the same issue.

    Any solution for this.?

    Thanks

    Vijay

  • HermannSW
    HermannSW
    4903 Posts

    Re: Error with Multi-Way results actions

    ‏2014-12-17T14:55:10Z  
    • Vijay97
    • ‏2014-12-17T14:19:46Z

     

    I am facing the same issue.

    Any solution for this.?

    Thanks

    Vijay

    Hi,

    the original thread is from 2011, the addon thread from 2013, and now we a more than a year later.

    Please attach a simple sample config demonstrating your problem, showing which firmware you have and what exactly the service does/should do.

    The error message itself does not allow more than guessing.


    Hermann.

    Updated on 2014-12-17T14:56:24Z at 2014-12-17T14:56:24Z by HermannSW
  • Vijay97
    Vijay97
    52 Posts

    Re: Error with Multi-Way results actions

    ‏2014-12-17T18:18:28Z  
    • HermannSW
    • ‏2014-12-17T14:55:10Z

    Hi,

    the original thread is from 2011, the addon thread from 2013, and now we a more than a year later.

    Please attach a simple sample config demonstrating your problem, showing which firmware you have and what exactly the service does/should do.

    The error message itself does not allow more than guessing.


    Hermann.

    I am using Datapower Firmware:XI52.6.0.1.0.    

    ​My service use case is  client -->MPGW ---> WSP --> Backend.

    Below is my configuration in MPGW.

    match-->Transform-->Results(Intermediate)-->Transform-->setVar(skip backside)-->Results 

    I have an intermediate Results action, and then a transform action to transform the response.

    I have set Process backend Errors on.

    Now , in the success scenario,, i.e when DP(MPGW) is receiving a success response from WSP, its working fine.

    But, if there is a validation error at WSP and it sends an error message. My MPGW is not receiving the response, it is showing error as it is not able to connect to backend url. and the logs say

    External URL protocol Error

    I verified WSP logs, it received the request and sent the response.

     

    My requirement is I wanted to capture the response from WSP in MPGW (both success and failure) and process it.

    But here, for Success scenario it works fine, but when WSP sends failure it doesn't.

     

    The only difference, I can see in WSP is when failure scenario. 

    var://service/error-headers string 'HTTP/1.1 500 Internal Server Error Content-Type: text/xml X-Backside-Transport: FAIL FAIL Connection: close '

    I tried setting the <dp:set-variable name="'var://service/error-protocol-response'" value="'200'" />

    ​But it dint help

     

    Appreciate your help..

  • HermannSW
    HermannSW
    4903 Posts

    Re: Error with Multi-Way results actions

    ‏2014-12-17T20:48:52Z  
    • Vijay97
    • ‏2014-12-17T18:18:28Z

    I am using Datapower Firmware:XI52.6.0.1.0.    

    ​My service use case is  client -->MPGW ---> WSP --> Backend.

    Below is my configuration in MPGW.

    match-->Transform-->Results(Intermediate)-->Transform-->setVar(skip backside)-->Results 

    I have an intermediate Results action, and then a transform action to transform the response.

    I have set Process backend Errors on.

    Now , in the success scenario,, i.e when DP(MPGW) is receiving a success response from WSP, its working fine.

    But, if there is a validation error at WSP and it sends an error message. My MPGW is not receiving the response, it is showing error as it is not able to connect to backend url. and the logs say

    External URL protocol Error

    I verified WSP logs, it received the request and sent the response.

     

    My requirement is I wanted to capture the response from WSP in MPGW (both success and failure) and process it.

    But here, for Success scenario it works fine, but when WSP sends failure it doesn't.

     

    The only difference, I can see in WSP is when failure scenario. 

    var://service/error-headers string 'HTTP/1.1 500 Internal Server Error Content-Type: text/xml X-Backside-Transport: FAIL FAIL Connection: close '

    I tried setting the <dp:set-variable name="'var://service/error-protocol-response'" value="'200'" />

    ​But it dint help

     

    Appreciate your help..

    Please attach a small sample config, and copy in complete error message (is it in request or erorr rule,?do you have an error rule?).

    Hermann.

  • Vijay97
    Vijay97
    52 Posts

    Re: Error with Multi-Way results actions

    ‏2014-12-17T21:09:27Z  
    • HermannSW
    • ‏2014-12-17T20:48:52Z

    Please attach a small sample config, and copy in complete error message (is it in request or erorr rule,?do you have an error rule?).

    Hermann.

    I dont have an error rule in MPG , I am processing everything in the request rule.

    It is working now, after adding

    <dp:set-response-header name="'x-dp-response-code'" value="'500 FAIL'"/>
    

    in WSP, error rule.

     

    Thank you.

     

  • HermannSW
    HermannSW
    4903 Posts

    Re: Error with Multi-Way results actions

    ‏2014-12-18T09:20:11Z  
    • Vijay97
    • ‏2014-12-17T21:09:27Z

    I dont have an error rule in MPG , I am processing everything in the request rule.

    It is working now, after adding

    <pre dir="ltr" style="color: rgb(0, 0, 0); word-wrap: break-word; white-space: pre-wrap;"><dp:set-response-header name="'x-dp-response-code'" value="'500 FAIL'"/> </pre>

    in WSP, error rule.

     

    Thank you.

     

    Not having a config I can only state that setting response stuff does not work in a request rule.

    Instead of using skip-backside mechanism with only a request rule, go against a HTTP Service Echo mode dummy backend on 127.0.0.1. Then in response rule you can generate or change the response based on request rule conditions, or you can do all processing in response rule. Please try that approach.


    Hermann.