# Webrick can not support such a request/response? **URL:** \ **Category:** Rails\ **Created:** [April 29, 2006, 10:27am UTC](https://www.ruby-forum.com/t/webrick-can-not-support-such-a-request-response/59161 "2006-04-29T10:27:55Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![charlie](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/d6d6ee/32.png) [@charlie](https://www.ruby-forum.com/u/charlie)\ **Post date:** [April 29, 2006, 10:27am UTC](https://www.ruby-forum.com/t/webrick-can-not-support-such-a-request-response/59161/1 "2006-04-29T10:27:55Z")
The following procedures: 1 Browser send a http request to controller A and wait for response 2 controller A send a http request to controller B and wait for response 3 Browser will not get the response unless controller A got response from controller B btw there exist only one pc for developing. Webrick can not support such a kind of request/response? From the log I traced i found that the connection that controller A want to establish with controller B will be return an error of time out. ---
**Author:** ![charlie](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/c/d6d6ee/32.png) [@charlie](https://www.ruby-forum.com/u/charlie)\ **Post date:** [April 29, 2006, 11:04am UTC](https://www.ruby-forum.com/t/webrick-can-not-support-such-a-request-response/59161/2 "2006-04-29T11:04:21Z")
That’s absolutely correct. A singe Webrick or Mongrel only supports one active Rails thread at a time. That thread takes the response, and issues another against the same Webrick or Mongrel. The second request cannot begin until the first completes, and the first cannot complete until the second completes, thereby giving a classic deadly embrace. – – Tom M.