|
Scott,
This
is the stack trace I am seeing:
~ThreadIf::join() <---- hang on
pthread_join()
~TransportSelector()
If you
look at ~UdpTransport() you see that shutdown() was called prior to join(), but
it is UdpTransport::shutdown() that gets called and it does not signal
the thread.
For
TCP, the same problem occurs:
~ThreadIf::join() <---- hang on
pthread_join()
~TcpBaseTransport()
~TcpTransport()
~TransportSelector()
The
problem occurs if TransportSelector::shutdown() is called to do a forced
shutdown prior to deleting stack objects.
Liz
Nope, it's not working. It's calling the the sub-classed
shutdown. I believe that is correct polymorphic behavior since
shutdown() is virtual.
To
explicitly call ThreadIf::shutdown, from ~ThreadIf() the call should be
written as ::shutdown(). This is an alternative solution to the one I gave.
If
I'm the only one to encounter this problem, I have to think that the Sun
compiler has made a different interpretation than the
others.
Thanks for looking into this.
Liz
Elizabeth,
I was just looking
at the code - it seems the threadIf shutdown is called from the ThreadIf
destructor - so the thread should die when the Transport is deleted.
Is this not working?
Scott
From:
Elizabeth Clark [mailto:elizabeth.clark@xxxxxxxxxxxxxxxxxxxxxx]
Sent: Thursday, February 03, 2005 9:37
PM
To:
'resiprocate-devel@xxxxxxxxxxxxxxxxxxx'
Subject: [reSIProcate] Transport
threads hanging on shutdown
When running the stack with
transport threads (multiThreaded =true), I find the transport threads are
not being shutdown. The Transport::shutdown() method hides
ThreadIf::shutdown() so it never gets called. I made this change which
works.
Index:
Transport.cxx
===================================================================
---
Transport.cxx (revision 3844)
+++
Transport.cxx (working copy)
@@ -62,6
+62,7 @@
{
// !jf! should use the fifo to
pass this in
mShuttingDown = true;
+
ThreadIf::shutdown();
}
|