[Catalyst] Self restarting test server for Win32!

Kiefer, Sascha sk at intertivity.com
Wed Nov 2 11:39:25 CET 2005


It's really not a easy one.
I suggest to seperate to rewrite the HTTPServer by seperating the work in to
scripts.
One that runs the server, the other one that checks:
1. the server is still runing; if not, restart it
2. checks whether or not the files have changed

Regards,
--esskar

> Update: Now, it happens to me also. I checked the return 
> values of bind and listen, but they seem to be okay. 
> The funny thing is, calling CTRL^C in the new CMD and 
> restarting the server by hand does not help either. 
> I have to close the CMD, open a new one and then start the 
> server again.
> 
> When I check TCPView to see the connected TCP ports, I see 
> that i have now 2 perl processes that both listen on port 3000. 
> So, we killed the cmd but not the perl.exe. But the process 
> that is also listen on port 3000 does no longer exist (checked 
> TaskMgr and list for that) and can not be killed by TCPView. 
> It is terminated though after i closed the CMD. So it might 
> be a problem with fork? under windows?
> 
> Regards,
> --esskar
> 
> > Hi,
> > 
> > Tested a little bit, and it actually looks good on my 
> machine (WinXP 
> > Home, AS Perl v5.8.7), but maybe it helps to check the 
> returnvalues of 
> > bind and listen. It may that the new server is started 
> before the old 
> > server process is terminated. That may result in 
> difficulties (...but 
> > should actually result in zero-returnvalue of accept...)
> > 
> > Regards,
> > --esskar
> > 
> > > -----Original Message-----
> > > From: catalyst-bounces at lists.rawmode.org
> > > [mailto:catalyst-bounces at lists.rawmode.org] On Behalf Of 
> Will Hawes
> > > Sent: Montag, 31. Oktober 2005 16:37
> > > To: The elegant MVC web framework
> > > Subject: Re: [Catalyst] Self restarting test server for Win32!
> > 
> > > On another note, I've been testing this patch a bit more today and
> > > I'm getting some unexpected results. The server restarts and is 
> > > functional the first time I modify a file. On the second 
> > > modification, the server restarts but seems not to bind 
> correctly to 
> > > port 3000. Port 3000 is totally non responsive unless I close the 
> > > command window and open a new one.
> > > 
> > > It's as though sockets are not released properly by Perl when you
> > > kill perl.exe or a parent process. I don't know why the restart 
> > > should work once and then fail and I haven't worked out 
> what to do 
> > > about it yet.
> > 
> > 
> > _______________________________________________
> > Catalyst mailing list
> > Catalyst at lists.rawmode.org
> > http://lists.rawmode.org/mailman/listinfo/catalyst
> > 
> 




More information about the Catalyst mailing list