Hi, the problem you are talking about seems to arise on Win32
too. Some weeks ago, we received the following report from Klaus
Triendl:
--------------------------------------------
i tested the SampleSocketServiceServer with linux and windows. under windows
an exception is thrown in StopServer().
i traced the problem and figured out that WSAGetLastError() in
Socket::connectError() returns WSAEFAULT (=10014L).
virtual void StopServer()
{
m_bQuitServer = true;
InetHostAddress host;
tpport_t port;
host = getLocal(&port);
//This is required so that CreateSocketPort can return.
TCPStream strm(host, port);
waitMutex.enterMutex();
waitMutex.leaveMutex();
}
if i change the code a little and the host is initialized with an address
other than 0, there is not such a problem.
virtual void StopServer()
{
m_bQuitServer = true;
InetHostAddress host("127.0.0.1");
tpport_t port;
getLocal(&port);
//This is required so that CreateSocketPort can return.
TCPStream strm(host, port);
waitMutex.enterMutex();
waitMutex.leaveMutex();
}
-----------------------------------------
Could you confirm if the same happens to you? You can also
read the whole thread on this mail list archives (September, thread
"exception in SampleSocketServiceServer::StopServer()"). We were
planning to add some checks on Win32, but if it is the same problem
what you are having on Solaris 9, we should probably add the checks
for all platforms.
On Sun, Oct 06, 2002 at 06:08:37AM -0400, Spinka, Kristofer wrote:
I haven't had the time to track anything down, however, if you try
running the portsample (SampleSocketPort.cpp), you will see the problem
immediately after the first client disconnects.
/kris
_______________________________________________
Bug-commoncpp mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/bug-commoncpp