Here you go, it's waiting in Sender.close() as seen from the stack. [root@localhost ~]# ps aux | grep amq root 48326 0.3 0.4 164584 7880 pts/0 Sl+ 16:09 0:00 ./amq-producer root 48347 0.0 0.0 103252 836 pts/2 S+ 16:10 0:00 grep amq [root@localhost ~]# pstack 48326 Thread 2 (Thread 0x7f77f570a700 (LWP 48327)): #0 0x000000336d0e9153 in epoll_wait () from /lib64/libc.so.6 #1 0x00007f77f5df4ecc in qpid::sys::Poller::wait(qpid::sys::Duration) () from /usr/local/lib64/libqpidcommon.so.2 #2 0x00007f77f5df4af5 in qpid::sys::Poller::run() () from /usr/local/lib64/libqpidcommon.so.2 #3 0x00007f77f5de94cb in qpid::sys::(anonymous namespace)::runRunnable(void*) () from /usr/local/lib64/libqpidcommon.so.2 #4 0x000000336d4079d1 in start_thread () from /lib64/libpthread.so.0 #5 0x000000336d0e8b5d in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f77f570e860 (LWP 48326)): #0 0x000000336d40b5bc in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f77f6728523 in qpid::sys::Condition::wait(qpid::sys::Mutex&) () from /usr/local/lib64/libqpidmessaging.so.2 #2 0x00007f77f672878f in qpid::sys::Monitor::wait() () from /usr/local/lib64/libqpidmessaging.so.2 #3 0x00007f77f6720ab6 in qpid::messaging::amqp::ConnectionContext::wait() () from /usr/local/lib64/libqpidmessaging.so.2 #4 0x00007f77f6720b19 in qpid::messaging::amqp::ConnectionContext::wait(boost::shared_ptr<qpid::messaging::amqp::SessionContext>) () from /usr/local/lib64/libqpidmessaging.so.2 #5 0x00007f77f671e7c4 in qpid::messaging::amqp::ConnectionContext::detach(boost::shared_ptr<qpid::messaging::amqp::SessionContext>, boost::shared_ptr<qpid::messaging::amqp::SenderContext>) () from /usr/local/lib64/libqpidmessaging.so.2 #6 0x00007f77f673c768 in qpid::messaging::amqp::SenderHandle::close() () from /usr/local/lib64/libqpidmessaging.so.2 #7 0x00007f77f6797965 in qpid::messaging::Sender::close() () from /usr/local/lib64/libqpidmessaging.so.2 #8 0x0000000000403738 in main (argc=1, argv=0x7fff0845f6b8) at ../amq-producer/main.cpp:43
-----Original Message----- From: Gordon Sim [mailto:g...@redhat.com] Sent: Tuesday, July 08, 2014 4:09 PM To: dev@qpid.apache.org Subject: Re: Potential qpid cpp 0.28 bug On 07/08/2014 09:40 AM, Duong Quynh (FSU1.Z8.IP) wrote: > Yes I did, I make clean, deleted the CMake_Cache.txt, redid the whole process > from "cmake .." if that doesn't work then something is wrong with the make > process. I'll wipe out the build folder and retry. That should certainly have done it. I just don't understand the log trace. Could you get a stack trace for all the threads (pstack <pid of producer process>), to be sure we know where it is waiting? (The protocol trace shows the session window is set to one message by the broker. Therefore only one message can initially be sent. The broker then does move that window forwards by one, which should allow another transfer to be sent. QPID-5737 fixes a case where this doesn't happen if the application is already closing the session.) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
