[GROOVY-4385] Response already committed on Google App Engine when serving blobs

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.7.4, 1.8-beta-1
• Fix Version/s: 1.7.5, 1.8-beta-2
• Component/s: Groovlet / GSP
• Assignee: Guillaume Sauthier
• Reporter: Guillaume Sauthier
• Created: 31/Aug/10 17:27
• Updated: 15/Dec/10 22:19
• Resolved: 31/Aug/10 17:30

Description

When using the BlobstoreService from Google App Engine to serve blob content from a Groovlet, whether through direct streaming or through getting an input stream / reader over the blob content, the GAE server would complain that the response is already committed.
What "commits" the response is the calls by GroovyServlet to response.setStatusCode() and response.flushBuffer().
The former sets the default 200 status code, which is usually set by default at 200 anyway by servlet containers.
The latter is also done by servlet containers when the servlet terminates.
At least, this is what I gathered from glancing through Tomcat and Jetty sources.
So the suggested fix is to remove the call to these two methods which "commit" the response too early.