The 1/2 Page load...

[MorpheusDreamlord]

I've noticed an error message in the log window which occurs on (before?) each 1/2 page failure..

** 2511 Socket Error 10038 for request flush **

'2511' obviously changes. Is this what's causing the 1/2 page load problem?... Anyone else seen this error

<Question/Problem: Socket operation on non-socket.

Answer/Solution: An operation was attempted on something that is not a socket. The specified socket parameter refers to a file, not a socket.
...Found this tho, maybe the problem is linked to local files?? (damn, I'm really scratching here.. LOL>

|
Come to the Dreaming...

Edited by - MorpheusDreamlord on 17 Jun 2002  18:45:01

[Scott Lemmon]

What request/reply does the connection number tie to?  Also exactly what filters are you using at the time and are you doing any RDIR's?

 

[Scott Lemmon]

I should also ask if anyone else is getting the same error.  Actually I'm not sure everyone is reporting the same problem, since you seem to also have crash problems the others don't. It's possible something is corrupting Proxomitron's memory, which could cause both types of errors.

Still, I need to know which URL the error ties to - the stylesheet or the page itself. No matter what I try I just can't get this to happen on my system - at least not with any of the filter sets I've tried.



 

[JD5000]

I've also gotten that error. I haven't seen it with the half loaded problem tho.

To test it, I went back to using <start> to insert css. At first I couldn't get the bug to reappear, but after I started editing my config & loading a crap load of pages, it came back.

This time I kept the log window open, but..

** 2511 Socket Error 10038 for request flush **

did not appear when the half loaded pages occured.

Although, I found by unchecking "Local connections persist for xx seconds" I was able to load the page without problems.

The problem was at Y!Groups.

~Just another blind stab in the dark. JD

--------

"Imagination is more important than knowledge" - Einstein

[Scott Lemmon]

quote:
I've also gotten that error. I haven't seen it with the half loaded problem tho.

Where have you seen the error then and are you sure it was that exact error (and not a similar one)?  

Also what timeout did you have on the local connections and how many connections do you have your browser set to make?





 

[JD5000]

At random places.. I just had one now.

+++GET 5200+++
GET /pforum/forum.asp?FORUM_ID=3 HTTP/1.1
User-Agent: Opera/6.03 (Windows 98; U)  [en]
Host: asp.flaaten.dk
Accept: text/html, image/png, image/jpeg, image/gif, image/x-xbitmap, */*
Accept-Language: en
Accept-Charset: windows-1252;q=1.0, utf-8;q=1.0, utf-16;q=1.0, iso-8859-1;q=0.6, *;q=0.1
Accept-Encoding: gzip, deflate
Referer: http://asp.flaaten.dk/pforum/
Cookie: <snip>
Cookie2: $Version="1"
TE: deflate, gzip, chunked, identity, trailers
Connection: keep-alive
+++CLOSE 5198+++
Client closed: total 3
Client closed: total 2
Connection Reused: 5198->5200
** 5200 Socket Error 10038 for request flush **
Connection Reused: 5182->5200
BlockList 5200: in CookieList, line 23

I have my timeout at 30.

My connections are at,

8 per server
12 Max

Although, I haven't seen Proxo show more then 8 active connections.

~JD

--------

"Imagination is more important than knowledge" - Einstein

[Bes]

I have those socket errors frequently too, although I do not have problems with images. Naoko 4.3 here.

 

[Scott Lemmon]

Just to let everyone know I've been looking into the error and I think I found the cause (of the error at least).  It's an attempt to reused a stale socket handle, but I'm not sure if it could be related to the half-loading bug or not.

In most cases the error would only cause Proxomitron to retry on a fresh connection, and this happens before the page begins to load (when the server is first contacted). Since you never know when a remote server will time out a connection, the program actually expects some sort of error at that point, but servers normally don't time-out actively downloading connections.

Anyway, here's something to try...

In = FALSE
Out = TRUE
Key = "If-Modified-Since: Always reload pages (Out)"
URL = "[^/]++local.ptron/"
Match = "*"

This (in a round-about way) should avoid the error causing the stale handle to be used, and might at least confirm/deny if it's the problem.

Thanks,

Scott





Edited by - Scott Lemmon on 19 Jun 2002  02:32:51

[Jor]

Hi Scott,

for me all problems disappeared after adding local.ptron to my bypass list.
Changing filters back to dhtml instead of local.ptron/ also works (but this doesn't work over a LAN).

I don't see why the 'site' local.ptron would have to be filtered in the first place, there can be no possible security risk attached, right?

 

[Scott Lemmon]

You should be able to bypass it without problems.  In fact I had considered just making it always bypassed, but there's the posibility someone may want to filter it for some reason - perhaps to add some dynamic element to the page.

 

[Jor]

quote:Anyway, here's something to try...

(filter)

This (in a round-about way) should avoid the error causing the stale handle to be used, and might at least confirm/deny if it's the problem.

Hi Scott, I just installed the last Opera bèta (6.04 b1129), and the half-loading pages reappeared. I have been following this topic with great interest of course, so tried the filter you posted: using the above filter does not prevent incomplete page loads, nor does the socket error message disappear. (The relation between this socket error message and incomplete loading pages is not as easy as it seems: the socket error message does not always appear with partially loaded pages, but if it appears, the page will not load completely).

The original page request still occasionally stops loading once prox.css is called -- but only if prox.css is included on <start>. Rewriting that filter according to altosax' suggestion completely eliminates the partial loads.

Edited by - Jor on 19 Jun 2002  15:11:34

[dave1006]

quote: The relation between this socket error message and incomplete loading pages is not as easy as it seems: the socket error message does not always appear with partially loaded pages, but if it appears, the page will not load completely

This is not my experience - I never get half-loaded pages (using 4.3 and opera 6.03), but I do occasionally get the socket errors - but to no ill effect seemingly.

-------------------------
|David Gallagher        
|dave at smokeajay.co.uk
-------------------------

[Scott Lemmon]

quote:
This (in a round-about way) should avoid the error causing the stale handle to be used, and might at least confirm/deny if it's the problem.

Hi Scott, I just installed the last Opera bèta (6.04 b1129), and the half-loading pages reappeared. I have been following this topic with great interest of course, so tried the filter you posted: using the above filter does not prevent incomplete page loads, nor does the socket error message disappear.
[/quote]

You might want to check that the filter is working properly.  If so you should never see a "Not modified" reply when Proxomitron is asked for a file from http://local.ptron/.  Check to make sure the If-Modified-Since: header is really being removed for local requests.

 

[Jor]

Ack... my mistake.

I had local.ptron in my bypass list, so this filter of course never matched.

It's working now, and indeed, no more partially loaded pages or socket errors.

 

[MorpheusDreamlord]

Now that WAS fun!!

I did this:

In = FALSE
Out = TRUE
Key = "If-Modified-Since: Always reload pages (Out)"
URL = "[^/]++local.ptron/"
Match = "*"

(I edit the .cfg, then save it and open it in proxo)...

BOOOOM!, wsock.vxd bsod, various other wsock(xxx).xxx errors (after pressing a key), then vmm.vxd died, and bingo!! auto reboot!!.

LOL!!

|
Come to the Dreaming...

Edited by - MorpheusDreamlord on 20 Jun 2002  16:45:14