World: r3wp

>> p: open/direct tcp://localhost:8002 close p p: open/direct tcp://localhost:8002 
print "ok"
close p
** Access Error: Cannot connect to localhost
** Near: p: open/direct tcp://localhost:8002 print "ok"
>>

the ok does not print because Cheyenne has quit

this though is fine


>> p: open/direct tcp://localhost:8002 print "ok" close p p: open/direct 
tcp://localhost:8002
print "ok" close p
ok
ok

so timing appears critical

Graham, I have to check my console, because I think mine auto-restarts 
on quit.

seems there is nothing in consle

meaning?

meaning it didn't quit

ok

well, reproducible on my system.

I guess we can make this group web-public again.

keep it non public, there is a wiki on cheyenneserver.org for open 
web

btw Henrik and I are running it on osx

http://cheyenne-server.org/..

maybe someone is attaking you http://ftp.uni-kl.de/25C3/video_h264_720x576/25c3-2909-en-tcp_denial_of_service_vulnerabilities.mp4
8P

Please let us know if there are any security vulnerabilities that 
pop up for Cheyenne, or REBOL network services for that matter.

I am about to use Cheyenne for a project that I have just found out 
will be more public than anticipated.,

Graham: no problem here, testing with 0.9.18 binaries and 0.9.19 
source version, can't reproduce that crash (all tests done on port 
80). WinXP-Pro-SP3 here.

I'm on vista and using port 8002

Do the Cheyenne processes disappear when your test fails? If not, 
did you try to access a web page to see if it's still responding?

try => tried

I'm watching the task manager ... all 3 cheynne processes quit

I think timing is critical for this bug to appear

ie. if I add a print between the open and close, the bug does not 
appear

I'm trying here with the code you've posted (without the print), 
but can't reproduce.

Hang on ...

http://screencast.com/t/cPpSejdtYZ

watch the task manager

Could you please try with the source version (v0.9.18) from here 
: http://cheyenne-server.org/dl/cheyenne-r0918.zip?

Btw, did you checked for a %crash.log file near cheyenne.exe?

ok. dl now

1-Jan-2009/9:16:46+13:00 : make object! [
    code: 305
    type: 'script
    id: 'invalid-arg
    arg1: true
    arg2: none
    arg3: none
    near: [set-modes new [no-delay: on]]
    where: 'init-connection
]

does that help?

forgot about crash.log

Ah, interesting.

still want me to test with source?

Yes, can you just comment the following line in %UniServe/uni-engine.r 
file :

	if new/scheme = 'tcp [set-modes new [no-delay: on]]

then try again your test.

Seems that Vista is more picky than XP about the usage of Nagle algorithm.

oops ...

>> do %cheyenne.r
Script: "Cheyenne Web Server" (19-Feb-2008)
** Script Error: NT-service? has no value
** Where: boot

** Near: if all [NT-service? not flag? 'service] [set-flag 'tray-only]
>>

Did you applied some TCP networking tweaks on your Vista box to improve 
network latency?

nope

REBOL/View 2.7.6.3.1 14-Mar-2008
Copyright 2000-2008 REBOL Technologies.  All rights reserved.
REBOL is a trademark of REBOL Technologies. WWW.REBOL.COM
>> do %cheyenne.r
make object! [
    code: 303
    type: 'script
    id: 'expect-arg
    arg1: 'context
    arg2: 'blk
    arg3: [block!]
    near: [extension-class: context list]
    where: func [/local list][
        list: extract phases 2
        forall list [change list to-set-word list/1]
        repend list [to-set-word 'service none]
        extension-class: context list
    ]
]
>>

Yes, old bug of 0.9.18 with REBOL 2.7.6.

Doc, do you have a time planned for the public release of 0.9.19?

Either use an older REBOL core or apply the following patch to Cheyenne 
: http://www.digicamsoft.com/cgi-bin/rebelBB.cgi?thread=<9May2008113928682359200>

BrianH: I should have released it a month ago, but some issues with 
RSP showed up and I like to fix them before releasing officially 
the new version.

I ['d] like...

Basically, some errors are not reported or (not catched?) during 
RSP execution. I want to clean up the RSP logging code to output 
all errors to a log file.

with no changes, Cheyenne no longer shuts down using the source version

using 2.6.2

Does that help?