[mapserver-users] Truncated msGMLOutput

[Daniel Morissette]

Yves Moisan wrote:
> 
> I wonder why though MS returns a malformed GML output instead of an
> error message.
> 

Quite likely because the GML output has already started when the error 
happens, and then it's too late to generate a valid OWS XML exception. 
We'd need to buffer the GML output (and potentially use lots of memory) 
to really do the right thing and produce an OWS XML exception in a case 
like this. The alternative would be to just dump the error message as a 
string at the end of the truncated GML ouptut which would be better than 
silently stopping as is happening now. You could file a ticket about 
this with some steps to reproduce the error if you feel that's worth it, 
but others may argue that's not a valid move.

Keep in mind that the best way to troubleshoot issues like this is 
MS_ERRORFILE/DEBUG... that's why we made those enhancements a few 
releases ago.

Daniel
-- 
Daniel Morissette
http://www.mapgears.com/