sockets timing out
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 64.25.47.16:443
where's the log file?
oh there's no file target?
okay thanks
no still nothing
it logs the message but not the excepton
:D
Maybe it's an issue in the version I'm using - 3.2
but I think it expects additional configuration
like you need to tell it how to format the exception
or it prints nothing at all
I don't know how to tamper with timeout values at the socket level
let's just all agree not to send 200 requests at the same time
wanna know why? to support the RichTextBox control in winfoms as a logging target
So, I think I'm satisfied with the PR on the PAO at this point. Any other changes your making on it before I merge it in and set the limit to 20?
instead of logging meaningless page numbers
but, I still don't know how to configure NLog to do that
I stopped getting socket timeouts when I changed the connection limit to 20
I don't know what the default is... I think 2?
it seems very likely that it would default to the number of cores
they use IIS for load balancing and whatnot
when we hit socket timeouts, that's their IIS actively refusing connection requests
as in basic DOS prevention