Greetings,

I'm relatively new to the framework so if you know something I do not,
I welcome being educated by those more familiar than I.  That said
I'll describe my discovery.

web2py on my server is deployed through WSGI+Apache2.
I also make use of ProxyPass directives to host multiple domains under
one box.

Now that I've set the scene, let's get to the story.  After editing
the default view of the particular application ( default/index.html of
course ).  I tried to navigate to the page.... status said "waiting
for <mydomain>".  30 seconds later, still said the same thing.  I
already had a putty session open so I checked top to see what the hell
the machine was doing.  Much to my suprise: apache2 was pegged on one
of the cpus ( 100% usage ).  Now, there's no reason anything in the
code should be working the machine that hard...even a fraction of that
hard - it's a very simplistic site thus far.  So I do some checking.
Every so many ( timeout of http connection? )seconds the access.log
reports a 502 error.  More checking....Everything seems ok but I still
have the same problem.  The other applications operate just fine.

Eventually, I see that I have a syntax error in one of the {{}} blocks
in the view.
So my question is: Is this how it is supposed to function or have I
discovered some off the wall bug?  I would have expected the
application to vomit some hideous error message into the browser
window and kill off the server process and allow apache and the
machine to continue to function.

Thoughts?

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py Web Framework" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to