[rabbitmq-discuss] Handle Stale Connections on Clients
monish.unni at gmail.com
Wed Jul 11 22:38:27 BST 2012
i also use spring-amqp and amqp inbound listener in spring-integration.
however, my issue is with reply-queue implementation of spring-amqp. i need
pre-made reply-queues that can be re-used (setup by configuration) even for
RPC semantics. i believe spring-amqp for RPC uses anonymous reply-queues and
also does consumer.cancel(benchmarks showed a 5ms delay for this on 24 core
cpu with broker and client running on the same box), which turns out to have
performance impact. thus, this rules out use of RabbitTemplate ( i wish it
had a way to use pre-made reply-queues that could be re-used).
thus, my wrappers around raw rabbitmq apis and even if i use
CachingConnectionFactory, i'd need to register a callback listener to
re-register my channels and reply-queues.
will definitely look at RabbitAdmin to learn how to do this.
thanks and regards,
Gary Russell wrote
> It shouldn't take much heavy lifting to use spring-amqp instead of the raw
> apis, and it will take care of reconnecting, setting up queues etc, via
> the ConnectionListener callback in the RabbitAdmin class.
> On the receiving side, you don't have to write any special listeners etc
> to use spring-amqp; you can just write your code as a POJO and the
> container uses an adapter to call your code. On the outbound side just use
> a RabbitTemplate; in most cases you can use high-level APIs, while still
> having access to the low level APIs (channel) if you ever need them.
> If you can't move to spring-amqp, you might be able to leverage some of
> the code from RabbitAdmin.
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Handle-Stale-Connections-on-Clients-tp20687p20725.html
Sent from the RabbitMQ mailing list archive at Nabble.com.
More information about the rabbitmq-discuss