Rick Marvin wrote: > Darin, I have been watching the nsAsyncStreamListener. I simply do not get > the OnDataAvailable event. My application is a console app which is testing > my library. My current idea is that there must be some setup step that I am > missing as I prepare my URI and Channel, for when I navigate to my https > address through the mozilla browser, I eventually get all the events I > expected. My console app is not running from the mozbin directory. Trying > to isolate the pieces of mozilla that my library really needs, I have set up > a directory hierarchy which includes its own "components subdirectory". I > use the nsMPFileLocProvider to establish my profile directory, placing the > psm-glue.js and security-prefs.js files there. The psm.exe resides in the > same bin directory as my console app exe. Although the windows task manager > shows that the psm.exe is running, it does not reflect any cpu-time. This sounds like the correct thing to do as an embedder. > > > Here is a copy of what the logging spits out if I have NSPR_LOG_MODULES set > to nsHTTPProtocol:5 > > 1300[4da6d8]: > nsHTTPRequest::OnStopRequest() [this=11728a8], aStatus=0 > 1300[4da6d8]: nsHTTPRequest [this=11728a8]. Finished writing request to > server. Status: 0 > 1300[4da6d8]: Creating nsHTTPResponseListener [this=1175d30] for URI: > https://galaxy.neoplanet.com/development/index.html. > 1300[4da6d8]: Creating nsHTTPServerListener [this=1175d30]. > 1300[4da6d8]: nsHTTPPipelinedRequest::WriteRequest()[11728a8], > mOnStopDone=1, mTransport=bfb524 > 1300[4da6d8]: nsHTTPServerListener::OnStartRequest [this=1175d30]. > > long period of no logging, then due to time out... What is the exact time out message? My guess would be that you are having some sort of trouble talking to psm. You said before that having a load group on the channel makes things work, right? Not sure where load groups would matter... but, at any rate, now we know that the problem is at the socket transport layer. I would suggest testing this by talking directly to the socket transport. You can enable logging in nsSocketTransport.cpp as well to help reveal what's going on. > > 1300[4da6d8]: nsHTTPServerListener::OnStopRequest [this=1175d30]. Status = > 804b000e, mDataReceived=0 > 1300[4da6d8]: nsHTTPChannel::ResponseComplete() [this=bf5fb0] > mDataListenet=115c640, Status=20022600016 > 1300[4da6d8]: Deleting nsHTTPFinalListener [this=115c640], created=1, > deleted=1 > 1300[4da6d8]: Deleting nsHTTPPipelinedRequest [this=11728a8], created=1, > deleted=1 > 1300[4da6d8]: nsHTTPHandler::ReleaseTransport [this=b506b8] i_pTrans=bfb524, > aCapabilites=0, aKeepAliveTimeout=0, aKeepAliveMaxCon=-1, maxKeepAlives=0 > 1300[4da6d8]: nsHTTPHandler::ReleaseTransport. Releasing socket transport > bfb524. > 1300[4da6d8]: nsHTTPHandler::ReleaseTransport():pendingChannels=0, > InUseCount=0 > 1300[4da6d8]: Deleting nsHTTPServerListener [this=1175d30]. Darin
