Description:
------------
Setup: 

Create a script that submits large messages to RabbitMQ using the AMQP extension, until the server starts to groan and produce log message alarms such as "vm_memory_high_watermark", indicating that it is running out of memory.

Once it gets past the high-water mark, it will sometimes continue to service requests, but eventually it appears to lock up and hang indefinitely. This can create a nightmare scenario for web sites that call rabbitmq as part of an end user's request.



Reproduce code:
---------------
sgfsd

Expected result:
----------------
The client library should eventually TIME out and give up on the server, throwing an exception. 

Actual result:
--------------
The client hangs indefinitely!


Proposed solution:

Please add a connection time out and a total time out option to each connection object and enforce it.  This may also require changes to the underlying C library rabbitmq-c.