Closed MichaelLangbein closed 1 year ago
I've tried restarting wps via the tomcat-manager; but the process does not come up again after being deactivated once.
Stopping and starting the container riesgos-wps
does the trick, though!
Closing: resolved with #60
Summary
xlin:href="http://localhost:8080/wps/RetrieveResultServlet?id=
, not asxlin:href="http://riesgos-wps:8080/wps/RetrieveResultServlet?id=...
docker compose -f docker-compose-with-wrappers.yml stop/start riesgos-wps
localhost
link; causing bad data to be stored in the filestorage.Noticed when ...
Downstream, this causes errors like the following when services further down the line attempt to make use of data from that wrong url
http://localhost:8080/wps/RetrieveResultServlet?id=
(from riesgos-wps logs):To reproduce:
Send a request to e.g. assetmaster:
The result contains a reference to a file:
This file will be stored in the filestorage. Inspecting that file we find the contents:
{"timestamp":"2023-01-13T17:02:53.101+00:00","status":404,"error":"Not Found","path":"/wps/RetrieveResultServlet"}