Topic
  • 2 replies
  • Latest Post - ‏2013-02-07T10:00:10Z by SystemAdmin
SystemAdmin
SystemAdmin
6772 Posts

Pinned topic ws proxy - response only returned when Back side timeout reached.

‏2013-02-05T14:34:01Z |
Hi,

We have set a back side timeout in a ws proxy to 10 sec.
For one of the services deployed in this ws proxy the behavior is that the Proxy only returns the response after the "Back Side Timeout" timeout setting time is reached, while the backend responds within 1-2 sec.
Changing the back side timeout settings changes the response time.
So e.g.
Back Side Timeout
set to 20 sec, serviceresponse is received after 20435 ms
set to 10 sec, serviceresponse is received after 10286 ms
set to 2 sec, serviceresponse is received after 2352 ms

We are using XI50.5.0.0.1

We already checked the answer in thread 345745 but that's not the issue in our case.
Anyone an idea?

Thanks.
Updated on 2013-02-07T10:00:10Z at 2013-02-07T10:00:10Z by SystemAdmin
  • HermannSW
    HermannSW
    4877 Posts

    Re: ws proxy - response only returned when Back side timeout reached.

    ‏2013-02-05T18:37:08Z  
    What you describe seems to indicate that your backend does not close the connection to DataPower.
    So DataPower does not know that the response received is complete and waits.
    The backend timeout then terminates backend connection and DataPower processes the (now known to be complete) response.

    You can take a packet capture on the interface to the backend.
    Doing a "Follow TCP Stream" eg. in Wireshark tool then and filtering for "tcp.port==yourbackendPort"
    you can see whether backend terminates the connection before timeout (FIN), or not.
    In case you see a FIN before backend timeout, please create a PMR.

     
    Hermann<myXsltBlog/> <myXsltTweets/>
  • SystemAdmin
    SystemAdmin
    6772 Posts

    Re: ws proxy - response only returned when Back side timeout reached.

    ‏2013-02-07T10:00:10Z  
    • HermannSW
    • ‏2013-02-05T18:37:08Z
    What you describe seems to indicate that your backend does not close the connection to DataPower.
    So DataPower does not know that the response received is complete and waits.
    The backend timeout then terminates backend connection and DataPower processes the (now known to be complete) response.

    You can take a packet capture on the interface to the backend.
    Doing a "Follow TCP Stream" eg. in Wireshark tool then and filtering for "tcp.port==yourbackendPort"
    you can see whether backend terminates the connection before timeout (FIN), or not.
    In case you see a FIN before backend timeout, please create a PMR.

     
    Hermann<myXsltBlog/> <myXsltTweets/>
    Thanks a lot for the quick response.

    We will trace like proposed.

    Cheers,
    Jeroen