(This message has been automatically imported from the retired mailing list)
we are having this problem on our servers running Zato, I guess it is a
matter of handling MySQL connection timeouts.
on the first request to Zato after some time of inactivitiy (e.g. the
first request in the morning), this error occurs.
We have two cases where this error occurs (on two different servers):
on our Jenkins server - during a build - we deploy our services by
copying them in the pickup dir, the deployment of the first service
fails (zato version 220.127.116.11)
for this error I attached a server log file
on the first request in web admin there’s an error page (zato
for this error I attached a web-admin error page