> I'm attempting to set up mod_webapp with Tomcat 4.0.3, but it segfaults.
> At least, I'm getting notifications of childern segfaulting in the error
> log, the webapp keeps restarting based on the initialization output, and
> submitting a request to Apache that is handled through the webapp yields
> a pre-mature disconnect.
A sign of Apache process dying before completing it's operation.
> I'm assuming it is segfaulting when attempting to serv a request.
Most likely.
> The question is why. The only misconfiguration I can think of is that I
> have not defined any application by name in the server.xml configuration
> file. I've added a directory to webapps/ and specified the name of that
> directory as the application name in httpd.conf.
No misconfiguration should lead to Apache (or any other software) segfaulting. It
should lead to an error message. Segfaults mean compilation trouble.
> Besides the load/addmodule stuff, this is that's in httpd.conf:
>
> WebAppConnection myWarp warp localhost:8003
> WebAppDeploy myApp myWarp /
>
> Tomcat is configured to listen to 8003 and I've verified it does
> (connecting with telnet yields junk - I'm assuming that is the Warp
> protocol).
>
> But again, I have done nothing to define any application called "myApp"
> besides creating the directory. I'm not sure if this is enough. But even
> if it isn't, I doubt a segmentation fault is the intended result.
Shouldn't segfault.
Nix.
