We've been getting intermittent issues calling web services from our Appian

Gavin Hume

Certified Senior Developer

over 10 years ago

We've been getting intermittent issues calling web services from our Appian cloud application. We occassionally get the following error (in this particular case the web service is called within a SAIL form using the webservicequery):
Error evaluating function 'webservicequery': The maximim time waiting for an operation to complete was reached (socket timeout).

Looking at the logs for this web service it returned a successful response after around 4 minutes but the error was displayed to the user before that response was sent. I assume there is some parameter/configuration setting that determines how long the webservicequery will wait for a response but am struggling to find out where it is set and what it is set to.

Can anyone help?...

Discussion posts and replies are publicly visible

0 venkateswarai917 over 10 years ago

which api used for webservice consumption?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 10 years ago

Once a connection is established, the number of seconds to wait for a response to a request is 60 seconds. Four minutes is a long time, especially if this is to be displayed on a form, this can definitely cause performance issues or at least an impression to the end user of poor performance if Appian waited so long to render the data. You may want to revisit your design or review why your web service is taking so long to respond.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Gavin Hume
Certified Senior Developer
over 10 years ago

Is the 60 seconds a fixed setting or can it be configured and if so how?

(In 75% of the cases the service responds in under 10 seconds and we are reviewing the design of the service to improve performance.)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 10 years ago

It is configurable but we don't recommend changing it because it can definitely give the users the impression that there's slowness in Appian while the bottleneck maybe your web service call which can make the end users believe there's a problem with the environment itself.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Gavin Hume
Certified Senior Developer
over 10 years ago

So how can we configure it (we might want to do this in our development environment so we can get the response, even if it's slow, so we can continue Appian development while we optimise the service)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 venkateswarai917 over 10 years ago

Uou will have to set the times in clinet code like this...

                     HTTPConduit http = (HTTPConduit) client.getConduit();
                     HTTPClientPolicy httpClientPolicy = new HTTPClientPolicy();
                     httpClientPolicy.setAllowChunking(false);
                     httpClientPolicy.setConnectionTimeout(36000);
                     httpClientPolicy.setReceiveTimeout(32000);
                     httpClientPolicy.setAutoRedirect(false);
                     http.setClient(httpClientPolicy);
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel