> > finally I found some time to investigate a bit further. > > - Using sysinternals tcpview, I could confirm that the > service is listening at port 8080. > - Using wireshark, I saw that the browser sends multiple > requests, but nothing comes back from the server. > > So I did a stack trace with the commandline version, and > accordingly set breakpoints in : > src/http/connection.C Ln 2115 Connection::handleRequest() > src/http/requestParser.C Ln 107 RequestParser::parseBody() > src/http/wtreply.C Ln 41 WtReply::consumeRequestBody() > > None of them was hit when debugging the service. > > So, what should I inspect next? > > Google brought me to CodeProject "RCF Interprocess > communication for C++" where someone talks about the same > behaviour with boost::asio. He fixed it with some threading macro. >
I don't know if this is applicable, but check to see under which account the service is running. I seem to recall that services under certain accounts won't have network access. Be sure your service is running under a full access account, and then slowly refine privileges. But then again, I could be way off base. One other thing to do... Make the software send something just to see that there is something happening. -- Scanned for viruses and dangerous content at http://www.oneunified.net and is believed to be clean. ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
