Grails

CLONE -GSP fails to write out entire response in Jetty

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 0.1
  • Fix Version/s: 0.3
  • Component/s: View technologies
  • Labels:
    None

Description

For some as yet unknown reason a GSP sometimes only writes out half the response when running in Jetty (works fine in tomcat). Jetty prints out the following message, it appears that the content length is not being set correctly at the time of writing in the GSPResponseWriter class.

[groovy] Invalid length: Content-Length=256 written=1045 for http://localhost
:8080/gcms/site/displayPage/6

Issue Links

is duplicated by

Bug - A problem which impairs or prevents the functions of the product. GRAILS-240 the view's layout can not work well

  • Blocker - Blocks development and/or testing work, production could not run.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Peter Kelley added a comment -

Clone of Grails-111

I am also seeing this problem (and yes it does work in Tomcat):

Invalid length: Content-Length=20 written=11197 for http://localhost:8080/requirements/useCase/show/1

The source of the page as reported by Firefox 2.0 beta is:

<html>
<head>
<ti

Using Grails 0.2.

Note: The data being displayed has come from a rich text source (Access via JDBC-ODBC and then inserted into HSQLDB) and so might contain "special" characters. I'm not sure if this is significant.

Show
Peter Kelley added a comment - Clone of Grails-111 I am also seeing this problem (and yes it does work in Tomcat): Invalid length: Content-Length=20 written=11197 for http://localhost:8080/requirements/useCase/show/1 The source of the page as reported by Firefox 2.0 beta is: <html> <head> <ti Using Grails 0.2. Note: The data being displayed has come from a rich text source (Access via JDBC-ODBC and then inserted into HSQLDB) and so might contain "special" characters. I'm not sure if this is significant.
Hide
Permalink
Peter Kelley added a comment -

Try link again: GRAILS-111

Show
Peter Kelley added a comment - Try link again: GRAILS-111
Hide
Permalink
Peter Kelley added a comment -

This is only happening on some records in a table and not others. I have analyzed the special characters (by looking at the \uxxxx values in HSQLDB) and the rows which do display are a superset of those that don't

Show
Peter Kelley added a comment - This is only happening on some records in a table and not others. I have analyzed the special characters (by looking at the \uxxxx values in HSQLDB) and the rows which do display are a superset of those that don't
Hide
Permalink
Peter Kelley added a comment -

By editing the markup of a particular page I was able to make some records display and others not. When one record started not displaying another would be able to be displayed.

Show
Peter Kelley added a comment - By editing the markup of a particular page I was able to make some records display and others not. When one record started not displaying another would be able to be displayed.
Hide
Permalink
Graeme Rocher added a comment -

Thing is it is difficult to tackle without a re-producably test case or sample GSP. If you extract the data from the db and paste it into a GSP (hence makin it not dynamic) does it exhibit the same behaviour? It does sound like an encoding issue.

Show
Graeme Rocher added a comment - Thing is it is difficult to tackle without a re-producably test case or sample GSP. If you extract the data from the db and paste it into a GSP (hence makin it not dynamic) does it exhibit the same behaviour? It does sound like an encoding issue.
Hide
Permalink
Jingang Zhou added a comment -

I am using Tomcat5.0 and Grails 0.2, the problem is even worse, some important content can not show because of the uncomplete response.

Show
Jingang Zhou added a comment - I am using Tomcat5.0 and Grails 0.2, the problem is even worse, some important content can not show because of the uncomplete response.
Hide
Permalink
Graeme Rocher added a comment -

Hey Peter,

If you disable the layout of the GSP does the problem go away? I just need to figure out if it is really related to GRAILS-240 which seems to be caused by the sitemesh layouts.

Thanks
Graeme

Show
Graeme Rocher added a comment - Hey Peter, If you disable the layout of the GSP does the problem go away? I just need to figure out if it is really related to GRAILS-240 which seems to be caused by the sitemesh layouts. Thanks Graeme
Hide
Permalink
Ford Guo added a comment -

I have the same error in 0.3 snapshot(svn trunk):
[groovy] Invalid length: Content-Length=10 written=8379 for http://localhost:8080/hello/node

Show
Ford Guo added a comment - I have the same error in 0.3 snapshot(svn trunk): [groovy] Invalid length: Content-Length=10 written=8379 for http://localhost:8080/hello/node
Hide
Permalink
Peter Kelley added a comment -

Turning the layout off in the header appears to "fix" the problem (the page is still broken but all the content is there so it's probably my fault)

Show
Peter Kelley added a comment - Turning the layout off in the header appears to "fix" the problem (the page is still broken but all the content is there so it's probably my fault)
Hide
Permalink
Graeme Rocher added a comment -

Not necessarily, if there is an error being thrown and Grails is "hiding" the error by cutting off half the page then that is a bug in my book

Show
Graeme Rocher added a comment - Not necessarily, if there is an error being thrown and Grails is "hiding" the error by cutting off half the page then that is a bug in my book
Hide
Permalink
Graeme Rocher added a comment -

I believe this has been fixed by GRAILS-303. Correct me if I'm wrong

Show
Graeme Rocher added a comment - I believe this has been fixed by GRAILS-303 . Correct me if I'm wrong
Hide
Permalink
Graeme Rocher added a comment -

I now have a reproducable test case

Show
Graeme Rocher added a comment - I now have a reproducable test case
Hide
Permalink
Graeme Rocher added a comment -

fixed for certain now. The length was being incorrectly calculated when the response buffer exceeded 8192 characters. It was only taking into account the characters from the second buffer and not the first (evil bug).

Show
Graeme Rocher added a comment - fixed for certain now. The length was being incorrectly calculated when the response buffer exceeded 8192 characters. It was only taking into account the characters from the second buffer and not the first (evil bug).
Hide
Permalink
Graeme Rocher added a comment -

Bulk closing bunch of resolved issues

Show
Graeme Rocher added a comment - Bulk closing bunch of resolved issues

People

  • Assignee:
    Graeme Rocher
    Reporter:
    Peter Kelley
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: