Databases
StackOverflow2013
Postsdbo
PORabbitMQ subscriber timeout
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORabbitMQ subscriber timeout
    primarykey
    data
    text
    <p>I have an issue when subscribing to RabbitMQ messages when traversing a CISCO ASA 5505 firewall. It appears there is some kind of timeout in the firewall which closes idle connections and results in my RabbitMQ subscription silently being dropped. The result is my subscriber doesn't throw/display any exception but doesn't receive published messages.</p> <pre><code>public class RabbitMqSubscriber&lt;T extends Serializable&gt; implements Subscriber&lt;T&gt; { private QueueingConsumer consumer; private MessageListener&lt;T&gt; listener; private String exchange; private String topic; public RabbitMqSubscriber(String host,String exchange,String topic) throws IOException { this.exchange=exchange; this.topic=topic; ConnectionFactory factory = new ConnectionFactory(); factory.setHost(host); factory.setRequestedHeartbeat(10); Connection connection = factory.newConnection(); Channel channel = connection.createChannel(); channel.exchangeDeclare(exchange, "topic"); String queueName = channel.queueDeclare().getQueue(); channel.queueBind(queueName, exchange, topic); consumer = new QueueingConsumer(channel); channel.basicConsume(queueName, true, consumer); } public void run() { while (true) { QueueingConsumer.Delivery delivery; try { delivery = consumer.nextDelivery(); Object o=SerializationUtils.deserialize(delivery.getBody()); listener.receive((T)o); } catch (ShutdownSignalException | ConsumerCancelledException | InterruptedException e) { throw new RuntimeException(e); } } } @Override public void setListener(MessageListener&lt;T&gt; listener) { this.listener=listener; } } </code></pre> <p>I've also tried adding keepalive to the server config but this hasn't helped either:</p> <pre><code>[ {rabbit, [{tcp_listen_options, [binary, {packet, raw}, {reuseaddr, true}, {backlog, 128}, {nodelay, true}, {exit_on_close, false}, {keepalive, true}]}]}]. </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USDD.
    1. USDD.
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PORabbitMQ subscriber timeout
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PORabbitMQ subscriber timeout
      1. USrobthewolf
      1. VTFavorite
    3. VO
      singulars
      1. PORabbitMQ subscriber timeout
      1. USDD.
      1. VTBountyStart
    1. COThis appears to be a firewall issue...works fine on intranet but not when passing through firewall.
      singulars
      1. PORabbitMQ subscriber timeout
      1. USDD.
    2. COYou could implement your own heartbeat messages to keep connections alive - you could have your subscriber send messages to the queue and receive them back again.
      singulars
      1. PORabbitMQ subscriber timeout
      1. USvladimir e.
 

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