Re: [Mongrel] [ANN] Mongrel 0.3.13.4 Pre-Release -- QUERY_STRING Fixed

[Jonathan del Strother]

I'm quite often losing mysql connections during requests, when using mongrel. Doesn't happen with lighty. This is on OS X 10.4.6, mysql 4.1.16, and a recent rails. Is there any other useful information I can supply?

On 17 Aug 2006, at 00:53, Zed Shaw wrote:

Hello Everyone,

I just posted another pre-release of Mongrel that fixes a bug which
caused Mongrel to claim it was getting parsing errors because the
QUERY_STRINGs were too long.  In actuality it was shift in the parser


Here's the full list of changes:

* It has a couple of fixes for win32, but I still have to apply a few
more patches from Jan Svitok.  This will happen tonight.
* The parser is fixed up to allow at least 10k QUERY_STRINGS.
* There is a new debugging feature.  You can now send any Mongrel
process a USR1 signal and it'll start dumping the full text and
parameters of any request it considers "bad".  More on this below.
* Tests were enhanced to test for the empty query string.
* The mongrel_cluster work from Bradley Taylor is now part of Mongrel
and will be maintained together so it'll get released at the same time
as mongrel.

the exception description.

That's all for now.  Please grab this release with:

  gem install mongrel --source=http://mongrel.rubyforge.org/releases/

And verify your application still works.


USR1 BAD CLIENT DEBUGGING

As mentioned above, if you're seeing BAD CLIENT messages or parsing

of what it received before aborting the client.

When you hit a parsing error, really make sure the client is correct,
then if you're positive it's right, send me the snippet from your log
(not all of your log) and I'll look at it.

When you're done, then simply hit the processes with another USR1 to
toggle it off.

The downside is I'm not sure of the security implications of this

not that bad to leave it on.


--
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?

_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users

that made empty queries (/test?) become negative. This is fixed up now. * Timeout errors now include the reason mongrel timed out the thread in errors from Mongrel then you can send your mongrel process a USR1 signal (unix only) and Mongrel will start dumping the full text and parameters change, but there's only a performance hit if the client is bad so it's

smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Mongrel-users mailing list
Mongrel-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-users