WebSphere Application Server & Liberty

Good morning,

A client application is calling a service running on liberty server and is getting a timeout in some of the request. Timeout is set to 2sg. Note that client is running in AWS Cloud, liberty running on-premises and the request is a HTTP POST with a JSON payload, so network latency maybe relevant.

I've activated the access logs in the liberty profile including a %D in the log format to get the response times. Even in the worse case, when the JSON payload is very heavy, the response time logged by liberty profile is never higher than 800 msg.

¿Does the response time reported by liberty include the time of serializing the payload? In other words ¿is counting the time since the client opens the input connection to write the payload?

If this is not the reason,¿How can be possible that the time reported by liberty is so different to the time perceived by the client when the timeout expires?

%D is the total elapsed time including network response time, so what you're observing is surprising. What framework does the client use to make the call? Does it make the call using a synchronous or asynchronous call?

Good morning,

A client application is calling a service running on liberty server and is getting a timeout in some of the request. Timeout is set to 2sg. Note that client is running in AWS Cloud, liberty running on-premises and the request is a HTTP POST with a JSON payload, so network latency maybe relevant.

I've activated the access logs in the liberty profile including a %D in the log format to get the response times. Even in the worse case, when the JSON payload is very heavy, the response time logged by liberty profile is never higher than 800 msg.

¿Does the response time reported by liberty include the time of serializing the payload? In other words ¿is counting the time since the client opens the input connection to write the payload?

If this is not the reason,¿How can be possible that the time reported by liberty is so different to the time perceived by the client when the timeout expires?

It is synchronous call, looks like the problem is related to some network mediation devices (Load Balancer, Gateways) implemented in the Cloud. 

%D is the total elapsed time including network response time, so what you're observing is surprising. What framework does the client use to make the call? Does it make the call using a synchronous or asynchronous call?

Good morning,

A client application is calling a service running on liberty server and is getting a timeout in some of the request. Timeout is set to 2sg. Note that client is running in AWS Cloud, liberty running on-premises and the request is a HTTP POST with a JSON payload, so network latency maybe relevant.

I've activated the access logs in the liberty profile including a %D in the log format to get the response times. Even in the worse case, when the JSON payload is very heavy, the response time logged by liberty profile is never higher than 800 msg.

¿Does the response time reported by liberty include the time of serializing the payload? In other words ¿is counting the time since the client opens the input connection to write the payload?

If this is not the reason,¿How can be possible that the time reported by liberty is so different to the time perceived by the client when the timeout expires?