Topic
  • 7 replies
  • Latest Post - ‏2013-03-25T20:39:00Z by GKReddy
SystemAdmin
SystemAdmin
6772 Posts

Pinned topic Retry using intermediate Results action

‏2013-03-22T21:00:27Z |
Hi,

I am working on a requirement which needs the WSP to retry the same Backend URL n times (in case of no response) before invoking the error rule.

I tried to achieve that by using an intermediate Results action by putting a context variable as Destination. The context variable contains the dynamic backend URL.

The issue is that i am getting a 0x00c3000f (Invalid URL error),instead of getting a Failed to Establish a back side connection error after trying the above configuration.

Please share your valuable suggestions/thoughts on what should be the correct way.

Regards,
Simmer
Updated on 2013-03-25T20:39:00Z at 2013-03-25T20:39:00Z by GKReddy
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Retry using intermediate Results action

    ‏2013-03-23T15:04:20Z  
    Hi Simmer,

    I guess you can try the same by using URL-OPEN in the xform. By this we can check the response received from the server and we can loop n number of times until you throw a dp:reject message.

    Hope this helps you.

    Regards,
    Dilip.
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Retry using intermediate Results action

    ‏2013-03-25T07:05:35Z  
    Hi Simmer,

    I guess you can try the same by using URL-OPEN in the xform. By this we can check the response received from the server and we can loop n number of times until you throw a dp:reject message.

    Hope this helps you.

    Regards,
    Dilip.
    Dilip - Thanks for your reply.
    But I am trying to avoid writing an xslt for achieving retry to the same URL.

    I am using the 'Number of Retries' option in the Results action.

    The only issue getting a invalid URL
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Retry using intermediate Results action

    ‏2013-03-25T07:11:17Z  
    Dilip - Thanks for your reply.
    But I am trying to avoid writing an xslt for achieving retry to the same URL.

    I am using the 'Number of Retries' option in the Results action.

    The only issue getting a invalid URL
    Dilip - Thanks for your reply.
    But I am trying to avoid writing an xslt for achieving retry to the same URL.

    I am using the 'Number of Retries' option in the Results action.

    The only issue is I am facing is I am getting a InValid URL error instead of 'Failed to establish a backside connection' (http)/Connection Error (https).

    I am specfiying the number of retries by populating destination with the help of a context variable in the intermediate result action , followed by another Results action.

    PLease share your thoughts.
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Retry using intermediate Results action

    ‏2013-03-25T09:27:34Z  
    Dilip - Thanks for your reply.
    But I am trying to avoid writing an xslt for achieving retry to the same URL.

    I am using the 'Number of Retries' option in the Results action.

    The only issue is I am facing is I am getting a InValid URL error instead of 'Failed to establish a backside connection' (http)/Connection Error (https).

    I am specfiying the number of retries by populating destination with the help of a context variable in the intermediate result action , followed by another Results action.

    PLease share your thoughts.
    Configuring Backend URL in results action or through Open-Url function will not give the actual backend failure messages.
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Retry using intermediate Results action

    ‏2013-03-25T09:27:52Z  
    Dilip - Thanks for your reply.
    But I am trying to avoid writing an xslt for achieving retry to the same URL.

    I am using the 'Number of Retries' option in the Results action.

    The only issue is I am facing is I am getting a InValid URL error instead of 'Failed to establish a backside connection' (http)/Connection Error (https).

    I am specfiying the number of retries by populating destination with the help of a context variable in the intermediate result action , followed by another Results action.

    PLease share your thoughts.
    Configuring Backend URL in results action or through Open-Url function will not give the actual backend failure messages.
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: Retry using intermediate Results action

    ‏2013-03-25T19:30:26Z  
    Configuring Backend URL in results action or through Open-Url function will not give the actual backend failure messages.
    You could have a intermediate result action with retry or a URL open where you do multiple retries.

    For both options, DP still requires a backend at the end of the rule. To solve it you have 2 options: skip-backside or use a loopback firewall.

    Regards,

    Fanny
  • GKReddy
    GKReddy
    138 Posts

    Re: Retry using intermediate Results action

    ‏2013-03-25T20:39:00Z  
    Dilip - Thanks for your reply.
    But I am trying to avoid writing an xslt for achieving retry to the same URL.

    I am using the 'Number of Retries' option in the Results action.

    The only issue is I am facing is I am getting a InValid URL error instead of 'Failed to establish a backside connection' (http)/Connection Error (https).

    I am specfiying the number of retries by populating destination with the help of a context variable in the intermediate result action , followed by another Results action.

    PLease share your thoughts.
    I think you should not be using context variable to set destination URL. The context variables are used to communicate between style-sheets locally.

    • GK