World: r3wp

So, why should I need to fall back to '*do ?

Webapps are, from v 19, contained in their own context (object!). 
'do will first bind the loaded code to the webapp context before 
executing it.

and if you're not using a webapp?

*do is just a fallback, if 'do is crashing your code ;-). It should 
be used, but as I had some context issues while testing with my own 
webapps, I've added it as a workaround while figuring out how to 
fix those issues.

if the RSP is not inside a webapp, then 'do will just call the native 
do.

Ok.  Thx

it should = it shouldn't

need R3

badly

That's why I was calling since the beginning of R3, for a focus on 
R3 Core features first, to be able to port our R2 code to R3 and 
benefit from modules (and other vital features like plugins). We 
reached PITS limits a long time ago.

I guess,most here are the same opinion

Anyone got a suggestion on how to modularise the app even more...

QM?

Uses RSP, and I think it can use some of Cheyenne's features too...

I was waiting for your input Chris!  Have you tested this out?

Tested -- yes it works.  I haven't had a chance to check installation 
against the latest version of Cheyenne though.

Please report back when you do ...

I'm not sure when I'll get the chance -- you can try the current 
installation procedure, ymmv...

Ok, it does work with version 0.9.18 (source version only)

we're up to 9.19 now

I'm still having problems with RSP not working every few days :(

Isn't software development fun!

Does it happen when you restart Cheyenne ?

Are you running several RSP webapps on the same server ?

not working
 means not responding or giving an error ?

I normally just reboot ... perhaps I need to find a cleaner way of 
killing the cheyenne process.
No, just the one RSP webapp.
Not responding.

I usually kill it here and start it again. For those times where 
it mysteriously just quits, I can also just start it again. I have 
mine set up via launchd in OSX.

This is not so good then .. is there a way we can debug this?

Or is it just Cheyenne reaching it's pool limit?

Henrik, are you running RSP, or CGI ?

RSP

It's a bug, but hard to fix because I can't reproduce it. The only 
way to fix it would be to log into a  Cheyenne server in blocked 
state, using the rconsole client.

So, if one of you can provide me with an access to a server in such 
state, I should be able to investigate on that issue.

Now my server quit. Doc, can we use that? I can't provide direct 
access to this server, but can you give hints on what to search for?

My quit as well... but i didn't see this message.  So I used 'kill 
to kill the pid and restarted it :(

Did you have to actually kill it?

how else?

Wait... I'll check my log.

Graham, mine just quits. I can go in and start it again without problems.

Mine is still running ... just RSP stops working.

29/10/08 21.56.24 com.apple.launchd[1] (com.rebol.cheyenne[65863]) 
Stray process with PGID equal to this dead job: PID 65868 PPID 65866 
rebol

I think launchd kills it for me.

There are 4 lines with that.

restarted it

If you can access to the server through rconsole just do this : write 
%debug.log mold uniserve (and put the compressed version of the %debug.log 
file on your web site so I can download it).

Ok

I take it that this is a new bug .. I'm still running a much older 
version of Cheyenne from last year ... and I never saw this.

( on a different server )

Henrik, if you're running cheyenne in source mode, you should use 
the -w command line option (that will allow the generation of a %crash.log 
file if the REBOL error is catched). If your Cheyenne quits, I don't 
think that's caused by a bug inside Cheyenne, but usually by something 
like an uncatched file access error (file handles starvation, file 
access rights,...). Will had some similar issues with Cheyenne on 
OS X, I guess he could help here.

Do you think the error is being caused by an untrapped Rebol error?

catched => caught
uncatched => uncaught