Hi Wim, Server::handleTcpAccept() is indeed called with an error. The error is : "system:995" Which according to the internet is most likely : "The I/O operation has been aborted because of either a thread exit or an application request."
In the commandline version, when I hit Ctrl-C, Server::handleTcpAccept() is also called with the 995 error. Also I added a message to Server::handleStop() which I don't see in the log files (neither commandline nor service). Rgds Richard On Sun, 2009-06-07 at 21:59 +0200, Wim Dumon wrote: > Richard, > > there is only one reason that I can think of why the threads are > exiting, and that is that asio believes that there is no more work to > do. Just after starting, the only task that is queued in asio is an > asynchronous accept. Right now, I don't see how port 8080 can be in > the LISTENING state while the accept call fails. > > Could you: > - Verify if Server::handleTcpAccept() in Server.C is called with an error > - check what this error is (if I'm not mistaken you can simply use > operator<< to cat it into a std::stream) > > Bye, > Wim. ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensing option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
