Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't see <code>amqp_consumer.py</code> or <code>amqp_producer.py</code> in the tarball, so reproducing the fault is tricky.</p> <p>RabbitMQ terminates connections, releasing their unacknowledged messages for redelivery to other clients, whenever it is told by the operating system that a socket has closed. Your symptoms are very strange, in that even a <code>kill -9</code> ought to cause the TCP socket to be cleaned up properly.</p> <p>Some people have noticed problems with sockets surviving longer than they should when running with a firewall or NAT device between the AMQP clients and the server. Could that be an issue here, or are you running everything on localhost? Also, what operating system are you running the various components of the system on?</p> <p><strong>ETA:</strong> From your comment below, I am guessing that while you are running the server on Linux, you may be running the clients on Windows. If this is the case, then it could be that the Windows TCP driver is not closing the sockets correctly, which is different from the kill-9 behaviour on Unix. (On Unix, the kernel will properly close the TCP connections on any killed process.)</p> <p>If that's the case, then the <strong>bad news</strong> is that RabbitMQ can only release resources when the socket is closed, so if the client operating system doesn't do that, there's nothing it can do. This is the same as almost every other TCP-based service out there.</p> <p>The <strong>good news</strong>, though, is that AMQP supports a "heartbeat" option for exactly these cases, where the networking fabric is untrustworthy. You could try enabling heartbeats. When they're enabled, if the server doesn't receive any traffic within a configurable interval, it decides that the connection must be dead.</p> <p>The <strong>bad news</strong>, however, is that I don't think py-amqplib supports heartbeats at the moment. Worth a try, though!</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to set timeout detection on a RabbitMQ server?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USTony Garnock-Jones
    1. USTony Garnock-Jones
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSorry about that. The producer and consumer is here http://blogs.digitar.com/jjww/code-samples/
      singulars
      1. PO
      1. USUnknown
    2. COI am running rabbitmq on a remote linux server while I am running the producer and consumer. I realize that the socket may not have been closed cleanly, but that is exactly what I want to emulate. I was testing to see how rabbitmq handles crashed processes which may not have closed the socket cleanly, and unfortunately it doesn't seems to handle this very well.
      singulars
      1. PO
      1. USUnknown
    3. CO@Tony; how does one enable the "heartbeat" option within the RabbitMQ server (within /etc/rabbitmq/rabbitmq.config for example)?
      singulars
      1. PO
      1. USRyan Duffield
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload