[rabbitmq-discuss] Make queue.bind after basic.consume (rabbitmq-c)

[Haster]

Hi there

Is it safety to call queue.bind after basic.consume?

I use this test case and sometimes my program hangs on:
0: c000000000546f10 : __syscall_0504() + 0x30 (/lib/hpux64/libc.so.1)
1: c0000000000257a0 : __recv() at /ux/core/lan/src/NET/libxnet/x_recv.c:34 
2: c0000000043e2080 : wchar_t() at amqp_socket.c:220 
3: c0000000043e24b0 : signed char() at amqp_socket.c:316 
4: c0000000043e2960 : signed char() at amqp_socket.c:385 
5: c0000000043d6be0 : signed char() at amqp_framing.c:1953 
6: c00000000a9b34d0 :
RabbitMQ::RabbitMQQueueImpl::bind(RabbitMQ::RabbitMQExchange*,std::basic_string<char,std::char_traits&lt;char>,std::allocator<char>
> const&)() at RabbitMQQueueImpl.cpp:167 

So maybe this test case is wrong and I should call basic.cancel befor I can
call queue.bind again?



--
View this message in context: http://rabbitmq.1065348.n5.nabble.com/Make-queue-bind-after-basic-consume-rabbitmq-c-tp27879.html
Sent from the RabbitMQ mailing list archive at Nabble.com.