When trying to launch my app, the container is unresponsive on the first try. When this happens, the following Error is shown on the browser:
Status code: 404
However, it is always successfully launched on the second try.
This is what appears on the ShinyProxy logs:
2018-01-12 18:31:11.292 INFO 34950 --- [ XNIO-2 task-5] c.s.docker.client.DefaultDockerClient : Starting container with Id: 68722ab696d5f124df724bc4a4749645fd542c0c22ae65121e6ae86ec2333b0d
2018-01-12 18:31:13.895 WARN 34950 --- [ XNIO-2 task-5] eu.openanalytics.services.DockerService : Container unresponsive, trying again (2/15): http://localhost:20000
2018-01-12 18:31:16.335 INFO 34950 --- [ XNIO-2 task-5] eu.openanalytics.services.DockerService : Proxy activated [user: 1G_XolpLntsR9dVy2554IS9SgyhxaJU2A5KIa7FV] [app: replid] [port: 20000]
After the last line appears on the logs, if I refresh the page on the browser, the app will be working correctly. However, other users may not know that refreshing once is enough (and it is inconvenient even if they do).
The inclusion of “container-wait-time” as an option has been very useful to me.
I was wondering if you think a configuration value that would function for container-wait-time similarly to how “heartbeat-rate” functions for “heartbeat-timeout” would fix this issue.
If so, do you have plans for (or would you consider) adding a configurable value like this in the future?
Thanks in advance,