Skip to Content
0
Feb 24, 2016 at 01:33 PM

Agentry Work Manager 6.2 transmit error, timout when fetching functional locations?

158 Views

Hi,

I'm not able to finish the Work Manager 6.2 initial synchronization due to an error "Communications Error (14)" when fetching functional locations.

With production data I have a huge amount of functional locations. Executing the The BAPI in the backend takes around 400 seconds, and I can see that when I do it using the iPad, it always fails around 300 seconds, which indicates some kind of timeout.

I increased the timeout values in SMP (SP09) for the backend connection from 300 to 600 and the problem is still happening. I think it is a problem between the client device and SMP 3.0 (not with the backend) because I can see the BAPI continues to be executed even after the iPad has been disconnected with the error.

In NGINX reverse proxy I increased all the timeouts at minimum 10 minutes and didn't change anything, see the values below:

http {

.

.

.

client_header_timeout 10m;

client_body_timeout 10m;

send_timeout 30m;

.

.

.

proxy_connect_timeout 1800;

proxy_send_timeout 1800;

proxy_read_timeout 1800;

.

.

.

server {

.

.

.

proxy_connect_timeout 1800;

proxy_send_timeout 1800;

proxy_read_timeout 1800;

.

.

.

}

}