|
In Rails 3.2 (and 3.1, and I don't know how much further back) on Glassfish, I seem to be getting buggy behavior with error messages.
In WEBrick, everything behaves as expected: I get an error message in the browser.
On GlassFish, when a 500 error is encountered (triggered, for instance, by <%= nonexistent_var %> in a view), the error is recorded in the server.log; however, no response body seems to be returned to the browser, so it times out.
Here's what that looks like with wget:
jamie@icf109118-Ubuntu:~/Documents/Aptana_Studio_3_Workspace/r32$ wget -S "http://icf109118-ubuntu:8080/r32/"
-2012-09-17 15:14:45- http://icf109118-ubuntu:8080/r32/
Resolving icf109118-ubuntu (icf109118-ubuntu)... 127.0.1.1
Connecting to icf109118-ubuntu (icf109118-ubuntu)|127.0.1.1|:8080... connected.
HTTP request sent, awaiting response...
HTTP/1.1 200 OK
X-Request-Id: 9c9be822cc04e5b84512b1410ad6067e
X-Runtime: 0.045000
Date: Mon, 17 Sep 2012 19:14:45 GMT
X-Rack-Cache: miss
Content-Type: text/html;charset=utf-8
Content-Length: 643
Length: 643 [text/html]
Saving to: `index.html'
0% [ ] 0 --.-K/s in 30s
2012-09-17 15:15:15 (0.00 B/s) - Connection closed at byte 0.
The lack of a response is confusing, and it also might be the underlying reason why I'm having trouble implementing custom 500 error messages.
|
