[rabbitmq-discuss] rabbitmq client timeouts, slow responses

[tsduncan]

I have figured out the problem on the server side. The broker has reached its
limit of socket descriptors.  That, I can resolve. 

I'd like to still understand if there is a timeout value in the Java client
that can be changed to have it wait longer before timing out. The connection
timeout and the sotimeout value on the socket do not seem to affect it.

Thanks



tsduncan wrote
> I have a rabbit configuration with about 50-60 rabbitmq clients. Some
> connect with python libraries and others with Java. After some time, new
> connections seem to take longer to process and the Java clients time out
> after 10 seconds.
> 
> com.rabbitmq.client.ShutdownSignalException: connection error; reason:
> java.net.SocketTimeoutException: Timeout during Connection negotiation
> 
> There are two issues I'd like to understand: 
> 1. why the server is taking so long to respond causing > 10 second
> responses
> 2. how to extend the java client timeout so they will wait longer than 10
> seconds. I cannot seem to find the right client side control that will
> extend the timeout beyond 10 seconds.
> 
> Here is some information on the client:
> Client Properties  {product=RabbitMQ, information=Licensed under the MPL.
> See http://www.rabbitmq.com/, platform=Java,
> capabilities={exchange_exchange_bindings=true,
> consumer_cancel_notify=true, basic.nack=true, publisher_confirms=true},
> copyright=Copyright (C) 2007-2013 VMware, Inc., version=3.1.0}
> 
> mqConnectionFactory.getConnectionTimeout() = 0
> mqConnectionFactory.getSocketFactory().createSocket().getSoTimeout() = 0
> mqConnectionFactory.getRequestedHeartbeat = 60
> 
> For the server side, I see the following in the logs for the client timing
> out:
> 
> =INFO REPORT==== 15-Oct-2013::13:47:19 ===
> accepted TCP connection on [::]:5672 from 172.24.1.197:33543
> 
> =INFO REPORT==== 15-Oct-2013::13:47:19 ===
> starting TCP connection <0.19149.1003> from 172.24.1.197:33543
> 
> =WARNING REPORT==== 15-Oct-2013::13:47:19 ===
> exception on TCP connection <0.19149.1003> from 172.24.1.197:33543
> connection_closed_abruptly
> 
> I will attach the full rabbit and sasl.log files.
> 
> 
> 
> clearbay at novamgmt12:/var/log/rabbitmq$ sudo rabbitmqctl status
> Status of node rabbit at novamgmt12 ...
> [{pid,2041},
>  {running_applications,
>      [{rabbitmq_management,"RabbitMQ Management Console","0.0.0"},
>       {rabbitmq_management_agent,"RabbitMQ Management Agent","0.0.0"},
>       {amqp_client,"RabbitMQ AMQP Client","0.0.0"},
>       {rabbit,"RabbitMQ","2.7.1"},
>       {os_mon,"CPO  CXC 138 46","2.2.7"},
>       {sasl,"SASL  CXC 138 11","2.1.10"},
>       {rabbitmq_mochiweb,"RabbitMQ Mochiweb Embedding","0.0.0"},
>       {webmachine,"webmachine","1.7.0-rmq0.0.0-hg"},
>       {mochiweb,"MochiMedia Web Server","1.3-rmq0.0.0-git"},
>       {inets,"INETS  CXC 138 49","5.7.1"},
>       {mnesia,"MNESIA  CXC 138 12","4.5"},
>       {stdlib,"ERTS  CXC 138 10","1.17.5"},
>       {kernel,"ERTS  CXC 138 10","2.14.5"}]},
>  {os,{unix,linux}},
>  {erlang_version,
>      "Erlang R14B04 (erts-5.8.5) [source] [64-bit] [smp:32:32] [rq:32]
> [async-threads:30] [kernel-poll:true]\n"},
>  {memory,
>      [{total,2521927344},
>       {processes,1984606400},
>       {processes_used,1984540336},
>       {system,537320944},
>       {atom,1351233},
>       {atom_used,1331305},
>       {binary,95355176},
>       {code,14331631},
>       {ets,365984592}]},
>  {vm_memory_high_watermark,0.3999999999821877},
>  {vm_memory_limit,13473855897}]
> ...done.





--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/rabbitmq-client-timeouts-slow-responses-tp30510p30562.html
Sent from the RabbitMQ mailing list archive at Nabble.com.