Thanks for your help Andrea,
>> - As soon as the InputStream is returned to the WPS executor, the job is >> marked as complete, even though it may take many hours to process and stream >> all the data. Additionally, any new WPS jobs are run immediately without >> respecting queue limits. > The queue is just for the "execute" phase. If you can change the code so that > it also does also the encoding in the execute thread, that would be > appreciated. We re-arranged our code to block in the execute phase with our second implementation (generating the complete response and writing it to file storage, before returning from execute). The apparent limitation is that the execute() method is also responsible for returning the RawData interface that supplies the InputStream which the wps extension code uses to return the response back to the client. This prevents any streaming of buffered content while it is being generated in a synchronous context - even if we use separate producer and consumer threads. Instead the wps execution IO workflow seems to be organized around discreet jobs. Is that an accurate description of the behavior? Cheers Julian University of Tasmania Electronic Communications Policy (December, 2014). This email is confidential, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone outside the intended recipient organisation is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender. The views expressed in this email are not necessarily the views of the University of Tasmania, unless clearly intended otherwise.
------------------------------------------------------------------------------
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
