Tsunami wrapper in production: runs indefinitely #98
Assignees
Comments
|
Does not work: <wps:Execute xmlns:wps="http://www.opengis.net/wps/2.0" xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wps/2.0 http://schemas.opengis.net/wps/2.0/wps.xsd" response="document" mode="sync" service="WPS" version="2.0.0">
<ows:Identifier>get_tsunamap</ows:Identifier>
<wps:Input id="lat">
<wps:Data mimeType="text/xml">
<wps:LiteralValue>-30.92143</wps:LiteralValue>
</wps:Data>
</wps:Input>
<wps:Input id="lon">
<wps:Data mimeType="text/xml">
<wps:LiteralValue>-71.37228</wps:LiteralValue>
</wps:Data>
</wps:Input>
<wps:Input id="mag">
<wps:Data mimeType="text/xml">
<wps:LiteralValue>6.85</wps:LiteralValue>
</wps:Data>
</wps:Input>
<wps:Output id="tsunamap" transmission="reference" mimeType="application/xml" schema="http://earthquake.usgs.gov/eqcenter/shakemap" encoding="UTF-8"></wps:Output>
</wps:Execute>Doesn't work, either ... even though it's one of AWIs pre-calculated simulations: <wps:Execute xmlns:wps="http://www.opengis.net/wps/2.0" xmlns:ows="http://www.opengis.net/ows/2.0" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wps/2.0 http://schemas.opengis.net/wps/2.0/wps.xsd" response="document" mode="sync" service="WPS" version="2.0.0">
<ows:Identifier>get_tsunamap</ows:Identifier>
<wps:Input id="lat">
<wps:Data mimeType="text/xml">
<wps:LiteralValue>-32.9011</wps:LiteralValue>
</wps:Data>
</wps:Input>
<wps:Input id="lon">
<wps:Data mimeType="text/xml">
<wps:LiteralValue>-71.8152</wps:LiteralValue>
</wps:Data>
</wps:Input>
<wps:Input id="mag">
<wps:Data mimeType="text/xml">
<wps:LiteralValue>8.5</wps:LiteralValue>
</wps:Data>
</wps:Input>
<wps:Output id="tsunamap" transmission="reference" mimeType="application/xml" schema="http://earthquake.usgs.gov/eqcenter/shakemap" encoding="UTF-8"></wps:Output>
</wps:Execute> |
|
Do we actually have an example execute request that works? @bpross-52n maybe? |
|
I just tested this execute request successfully: |
MichaelLangbein
changed the title
|
I tried to narrow down the reason for this error. The values for lat, lon and mag have to be as in the pre-calculated simulations. Otherwise the WPS responds with the exception message If it is not the WPS Client Lib it could still be:
|
|
@arnevogt , @bpross-52n : my second request in this comment didn't work because it used WPS-V2. With WPS-V1 syntax it does indeed work fine. @arnevogt : did you deploy your changes to production? |
|
@arnevogt : I have deployed the latest state of main branch to production. Tsunami wrapper does work fine if the input is an earthquake that tsuami-wps knows about. Here's the tsunami-wrapper log for an order with mag < 8: |
|
@MichaelLangbein Confirm that the wrapper is still stuck if the input values don't match a pre-calculated simulation. The issue itself is related to the PyWPS/get_tsunamap process. From the log you can see that WPS (not the wrapper) is stuck during the third retry. I don't know why the WPS behaves like this, but this is repeatable also with the GIST I wrote. |
I've created an issue at https://gitlab.awi.de/tsunawi/tsunawi/-/issues/2 , but since this is a private repo, I'm keeping this one open. |
|
I also created a new issue regarding the timeout for the wrapper because the case that a WPS process is stuck can (in theory) happen with all processes. |
Alright, I can confirm that the wrapper is still stuck if the input values don't match a pre-calculated simulation. I am, however, not certain that the issue is with PyWPS/get_tsunamap. Simply sending an execute-request with postman several times does not cause py-wps to stop responding. I can reproduce the error only with the production-environment and with your GIST. |
|
BTW: my intellij debugger gives the following output when running that GIST: Not sure why there is a |
|
@MichaelLangbein |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In production, the tsunami wrapper never gets further than the state
running.Here's the docker-log for the tsunami wrapper after receiving an order:
The text was updated successfully, but these errors were encountered: