Your Apache log looks good to me. When servlets throw uncaught exceptions,
as the Error example does (on purpose), several things happen. See:
Ironically, you happened upon the one action that isn't described in the
docs: the traceback and exception are printed to stderr, which is typically
logged by the web server.
On my TO DO.
At 04:32 PM 1/24/2001 -0500, Eli Green wrote:
>Since the current trend seems to be moving away from proprietary adapters
>and going with more common methods of communicating with the server, I
>thought I'd finish that stupid FastCGI all-in-one-process server that I
>started aeons ago. Since FastCGI and the adapters do essentially the same
>thing, I figured it wouldn't be a hideous thing to have lying around.
>I'm also bored.
>In any case, all works well and quite speedily until I try and access the
>Error example, when I get this in apache's error log:
>[Thu Jan 25 04:50:03 2001] [error] WebKit: Error while executing script
>Traceback (most recent call last):
> File "Application.py", line 300, in dispatchRequest
> File "Application.py", line 408, in handleGoodURL
> File "Application.py", line 481, in respond
> File "./Transaction.py", line 93, in respond
> File "HTTPServlet.py", line 38, in respond
> method(self, trans)
> File "./Page.py", line 33, in respondToGet
> File "./Page.py", line 52, in _respond
> File "./Page.py", line 100, in writeHTML
> File "Examples/Error.py", line 8, in writeBody
> import UnknownModule
>ImportError: No module named UnknownModule
>My question is why the call to handleGoodURL (Application.py:300) isn't
>being caught by the try/except block surrounding it. Is there a limit to how
>far this stuff will nest? I didn't think so, but ...
>Webware-discuss mailing list