PureEngage On-Premises

 View Only

Sign Up

Expand all | Collapse all

Port not closing after webservice block fails

  • 1.  Port not closing after webservice block fails

    Posted 06-30-2016 10:21

    Hi Guys using version 8.1
    I have simply using web service block for HTTP restful request to call a webserver. I have setup the webserver to not respond to the clients request in this case genesys and set the http_conn_idle_timeout in http section of URS to 9 seconds. Naturally it should go into the block and come out of red port after 9 seconds in which server hasnt responded to the request and the client socket should be closed for the next connection.

    It does come out of the redport but i can see the port of the webserver still to established and not getting closed. Im alos looping the request so once it fails and comes back to webservice block another httpbridge process gets created and they start to stack.Shouldnt it get closed after webserver has not responded to the request. I can see in the URS HTTP logs that socket remains opened

    Is there any config option I am missing? Please suggest guys


  • 2.  RE: Port not closing after webservice block fails

    Posted 07-04-2016 07:14
    Anyone?