As we experienced with #98 processes can be stuck an will never return a result (neither success nor error).
In consequence the wrapper/job remains in "running" state forever.
To recover from this state the wrapper needs to implement a timeout after which a process is considered to be failed.
(Check if the WPS Client already has a timeout mechanism.)
As we experienced with #98 processes can be stuck an will never return a result (neither success nor error). In consequence the wrapper/job remains in "running" state forever.
To recover from this state the wrapper needs to implement a timeout after which a process is considered to be failed.
(Check if the WPS Client already has a timeout mechanism.)