[rabbitmq-discuss] STOMP Error?

Darien Kindlund darien at kindlund.com
Fri Feb 6 19:30:29 GMT 2009

Hi Matthias,

Okay, that makes sense. Couple of questions:

1) Is there any sort of default idle timeout in RabbitMQ or the STOMP  
connector, where idle connections are terminated by the server?

The reason I ask, is that the 75 STOMP connections may be idle for  
upwards of an hour and then be tremendously bursty. So, you're saying  
that keeping the connections alive would resolve these RabbitMQ  
errors, right?

2) The data I'm working with can be shared. That said, I'm wondering  
if LShift could install the latest STOMP adapter on dev.rabbitmq.com  
so I could replicate future issues on that server, making it easier to  
troubleshoot from your end. Just a thought.

-- Darien

On Feb 6, 2009, at 12:18 PM, Matthias Radestock <matthias at lshift.net>  

> Darien,
> Darien Kindlund wrote:
>> -rw-r--r-- 1 rabbitmq rabbitmq 158842429 2009-02-05 16:44  
>> rabbit_persister.LOG
> That's a non-negligible amount of persisted data. The persister  
> writes a new snapshot every 500 events (publishes, acks, etc).  
> Writing ~160MB of data to disk could take a few seconds. The  
> persister is queried by channels the first time they need a guid,  
> e.g. for generating names of auto-delete queues or unique ids of  
> persisted messages. That call might time out when the persister is  
> in the middle of writing a snapshot. The error you are seeing is a  
> result of that.
> We will remove the dependency of the guid generation on the  
> persister in the next release, at which point you should no longer  
> see the error.
> Meanwhile you can reduce the likelihood of the error occuring by  
> reducing the frequency with which you establish new connections,  
> e.g. by keeping them open for longer and re-using them, reducing the  
> rate at which you publish persisted messages, or turning off message  
> persistence altogether.
> Regards,
> Matthias.

More information about the rabbitmq-discuss mailing list