[rabbitmq-discuss] STOMP error report: client_timeout

[Michael Justin]

Hello! Will the RabbitMQ 3.3.2 server STOMP plugin log client_timeout 
errors like the one below when the client connection dies and the Stomp 
client-side heartbeat stops? A user of my Stomp library reports that 
this error message appears frequently in a RPC system.

The RPC architecture is:

* Stomp clients (1000+) + Java AMQP 
servers(several)---HAproxy---RabbitMQ (cluster of two nodes)

Further information I received from the user:

* client time-out parameter of HAproxy is set to 120 seconds
* heart-beat parameter of RabbitMQ is set to 580 seconds
* Stomp client-side heart-beat parameter 10 seconds, no server heart-beats

I can imagine that the server operating system will keep the Stomp 
connection in TIME_WAIT state for a while after a client crash and the 
server will detect missing Stomp heart-beats if there is no more pending 
data in the socket. Would this be a potential cause of this log message?

Regards

=ERROR REPORT==== 15-May-2014::08:32:20 ===
** Generic server <0.4515.272> terminating
** Last message in was {'$gen_cast',client_timeout}
** When Server state == 
{state,"session-aVUZrMRW4ccDAF85RFj53Q",<0.4509.272>,
                             <0.4523.272>,
                             {dict,0,16,16,8,80,48,
 
{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                  []},
 
{{[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                   [],[]}}},
                             "1.0",#Fun<rabbit_stomp_reader.1.84385891>,
                             undefined,
 
{stomp_configuration,"guest","guest",false,false},
                             {set,0,16,16,8,80,48,
 
{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                  []},
 
{{[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                   [],[]}}},
                             {dict,0,16,16,8,80,48,
 
{[],[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                  []},
 
{{[],[],[],[],[],[],[],[],[],[],[],[],[],[],
                                   [],[]}}},
                             #Fun<rabbit_stomp_util.trim_headers.1>,
                             {amqp_adapter_info,
                                 {0,0,0,0,0,65535,2672,9740},
                                 61613,
                                 {0,0,0,0,0,65535,2669,58582},
                                 50861,
                                 <<"10.109.228.214:50861 -> 
10.112.38.12:61613">>,
                                 {'STOMP',0},
                                 [{ssl,false}]},
                             #Fun<rabbit_stomp_reader.0.123360627>,none}
** Reason for termination ==
** client_timeout

2, erlang's report:

=CRASH REPORT==== 15-May-2014::08:32:20 ===
   crasher:
     initial call: gen:init_it/6
     pid: <0.4515.272>
     registered_name: []
     exception exit: client_timeout
       in function  gen_server2:terminate/3
     ancestors: [<0.4506.272>,rabbit_stomp_client_sup_sup,rabbit_stomp_sup,
                   <0.259.0>]
     messages: [{'EXIT',<0.4523.272>,{shutdown,normal}}]
     links: [<0.4506.272>]
     dictionary: [{guid_secure,{{4,rabbit at fqmq1,#Ref<0.0.314.394>},0}}]
     trap_exit: true
     status: running
     heap_size: 987
     stack_size: 27
     reductions: 1097
   neighbours:
=SUPERVISOR REPORT==== 15-May-2014::08:32:20 ===
      Supervisor: {<0.4506.272>,
                                            rabbit_stomp_client_sup}
      Context:    child_terminated
      Reason:     client_timeout
      Offender:   [{pid,<0.4515.272>},
                   {name,rabbit_stomp_processor},
                   {mfargs,
                       {rabbit_stomp_processor,start_link,
                           [{stomp_configuration,"guest","guest",false,
                                false}]}},
                   {restart_type,intrinsic},
                   {shutdown,4294967295},
                   {child_type,worker}]