Hm. Well. Let's see. Can you say something about if the connection times
out or if it aborts immediately (e.g., never even establishes a
connection)?! If the first, then it's likely to be a Comanche problem -
I just tried a little test where I did the following:
[host]
s := Socket newTCP.
s listenOn: 12345 backlogSize: 4.
(yes, there is no loop accepting connections)
[client]
1 to: 100 do:[:i|
s := Socket newTCP.
s connectTo: NetNameResolver localHostAddress port:
12345.
].
Then I went out for a smoke and when I just came back I accepted the
sockets on the host. All fine, all connected. So that seems to work
okay. A little aside: The reason the above works (even with a backlog
size of four) is that internally the VM accepts an arbitrary number of
connections (limited by available memory; it's roughly 100 bytes pro
connection so you can have _plenty_ ;-)
If it's just not connecting, then it's likely that the connections come
in too close to each other. Considering that scheduling sucks big time
on Windows it's possible that the accepting thread (which is run at high
priority) just can't accept all the connections fast enough (and it
might even get preempted by Word or some other stupid app - you wouldn't
_believe_ the stories I can tell you about Windows - in particular NT -
scheduling). The solution to this problem might be to increase the
backlog size to something ridiculously large (like a hundred or so).
This should give the TCP layer enough buffers to accept the connections
on the interrupt level. It's not really recommended to use that many
buffers but considering that you really don't want to have two
webservers running on the same machine it seems like a pretty reasonable
solution for Comanche. If that doesn't work either, then I need a test
case - I have a Win2K machine but I need something that actually
triggers the behavior (reliably if possible).
Cheers,
- Andreas
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On Behalf Of Jochen F. Rick
> Sent: Tuesday, February 05, 2002 10:35 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [pws] Problem with Swiki not serving images
>
>
> Hi Andreas,
>
> thanks for the fixes, but it did not solve the Win2k ComSwiki
> problems.
> We just tried it out and still couldn't get the adminTool to
> work properly.
>
> Peace and Luck!
>
> Je77
>
> On Tue, Feb 05, 2002 at 09:00:15PM +0100, Andreas Raab wrote:
> > I'd be interested to see if the problem goes away if you
> use the VM from
> >
> >
> http://isgwww.cs.uni-magdeburg.de/~raab/squeak/alpha/SqueakNetFix.zip
> >
> > Background: I've recently had the need to run some heavy-duty collab
> > stuff which used between 10-100 TCP connections connections
> per second
> > (since we hadn't implemented UDP yet, we just used
> extremely short TCP
> > bursts of data ;-) That was a lot of fun and it also exposed two
> > fundamental problems in the networking code (as you might guess with
> > these connection rates you get pretty much every impossible
> situation if
> > you just keep it running for an hour...) One of the
> problems was rather
> > stupid since the comment said the right thing just the code
> didn't do it
> > (ouch!) and the other one was a misunderstanding of the
> WinSock specs on
> > my part (all but two codes returned by WSAGetLastError means your
> > connection is dead and I only handled one of all the "bad"
> errors). Both
> > were _serious_ problems which sometimes led to endless loops on the
> > Squeak side (which, btw, might explain some of the other
> effects people
> > have seen with Comanche+Windows).
> >
> > So assuming that this is no Comanche problem this VM might
> just solve
> > the problem. Please make sure you replace the "right" VM
> with the above
> > one (some people use multiple VMs and then you might
> replace the wrong
> > one and wonder what's up - so I recommend searching your
> hard disk for
> > any Squeak.exe's to see where they are).
> >
> > Please let me know if the above works any better or not. It
> certainly
> > did work in my last demos (which run the collab stuff
> between machines
> > with XP and Win2K).
> >
> > Cheers,
> > - Andreas
> >
> > > -----Original Message-----
> > > From: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]] On Behalf Of Jochen F. Rick
> > > Sent: Tuesday, February 05, 2002 3:49 PM
> > > To: [EMAIL PROTECTED]
> > > Subject: Re: [pws] Problem with Swiki not serving images
> > >
> > >
> > > Win2k is a problematic Swiki server. You should set up
> the external
> > > server. Again, check that out in the help guide to the
> admin utility.
> > >
> > > Peace and Luck!
> > >
> > > Je77
> > >
> > > On Mon, Feb 04, 2002 at 02:38:42PM -0600, Jeff Stewart wrote:
> > > > The server platform is Windows 2000 Pro. I don't mind
> > > serving the icons from a separate server (how?) but I have
> > > some pages that have lots of diagrams, and those diagrams are
> > > page attachments. I have no idea how to get the Swiki to
> > > serve pages, have A
> > > pache serve images, and keep all existing Swiki upload/attach
> > > functionality.
> > > >
> > > > --
> > > > Jeff S.
> > > > http://object01.go.dyndns.org
> > > >
> > > > ----- Original Message -----
> > > > From: Jochen F. Rick
> > > > To: [EMAIL PROTECTED]
> > > > Sent: Monday, February 04, 2002 12:42
> > > > Subject: Re: [pws] Problem with Swiki not serving images
> > > >
> > > >
> > > > What server platform are you running under? On some
> of our linux
> > > > machines, we serve icons through Comanche (minnow for
> > > instance). We had
> > > > the same problem you had serving off MacOS. I'm pretty
> > > sure this is more
> > > > of a VM problem than a Comanche one. Cross-platform
> > > networking is hard.
> > > > You will probably want to sot up an external server to
> > > serve the icons.
> > > > Check that out in the help guide to the admin utility.
> > > You should be able
> > > > to use some part of your port 80 apache server to serve icons.
> > > >
> > > > Peace and Luck!
> > > >
> > > > Je77
> > > >
> > >
> >
>
