[rabbitmq-discuss] Getting SocketTimeoutException on java Producer client during load testing

[Michael Klishin]

Sean Stephens:

> My belief at this point is that my producer load has overrun the connection factory pool in writing to the queues.
> 
> I have been unable to locate information on settings related to the connection factory pool to make it larger or change the timeout.  When the connections do timeout, it doesn't look like the pool catches up unless I kill the Producer application.  Anyone have advice on how to get past this issue?

ConnectionFactory does not pool connections. Can you take a look at rabbitmq log to see if
there are any warnings about alarms and blocked publishers?

> Is there a way to throttle the load at the Producer connection, or will it be necessary to just add more nodes to handle the incoming load?

You can implement throttling logic in your own code but in general, you need to have enough
consumer capacity to keep up with producers, or RabbitMQ will block connections that publish
(there will be a very visible warning in the log).

MK



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130911/496fe5bd/attachment.pgp>