[Bese-devel] UCW: Problem with cmucl

[Marco Baringer]

i admit to being very confused. The complete lack of output seems very 
strange, not even an error message.

On Mercoledì, mar 10, 2004, at 09:32 Europe/Rome, Giannandrea Castaldi 
wrote:

> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address           Foreign Address         
> State
> tcp        0      0 0.0.0.0:111             0.0.0.0:*               
> LISTEN
> tcp        0      0 127.0.0.1:33010         0.0.0.0:*               
> LISTEN
> tcp        0      0 0.0.0.0:23              0.0.0.0:*               
> LISTEN
> tcp        0      0 0.0.0.0:3001            0.0.0.0:*               
> LISTEN
> tcp      494      0 127.0.0.1:3001          127.0.0.1:33069         
> ESTABLISHED
> tcp        0      0 127.0.0.1:33009         127.0.0.1:33008         
> ESTABLISHED
> tcp        0      0 127.0.0.1:33008         127.0.0.1:33009         
> ESTABLISHED
> tcp        0      0 127.0.0.1:33011         127.0.0.1:33010         
> ESTABLISHED
> tcp        0      0 127.0.0.1:33010         127.0.0.1:33011         
> ESTABLISHED
> tcp        1      0 127.0.0.1:3001          127.0.0.1:33015         
> CLOSE_WAIT

why is 127.0.0.1:3001 both ESTABLISHED and CLOSED_WAIT?

> I've seen that someone else have problems in using ucw+cmucl, Is there 
> someone that use both wihout problems?

it doesn't seem so.

ok, could you do me a favor: could you load the examples and then, 
before making a request from the browser, inspect the *default-server* 
object's backend slot? how many active processes are there and what 
state are they in? If you try some of the other examples (try 
/ucw/examples/hello-world.ucw), what happens?

thanks,
--
Marco
Ring the bells that still can ring.
Forget the perfect offering.
There is a crack in everything.
That's how the light gets in.
	-Leonard Cohen