Hi everyone!!! For the first, let me tell you I've already had a look around on tomcat faqs, bugs, and stuff like that, wher I found nothing about this strange thing is happenning to me...
The "thing" is: I've been working pretty comfortable and easily with tomcat 4.0 and mod_webapp. That connector is like heaven. No configuration, no additional files, no worries about multiple hosts, and so on. I'm running a classical redhat system, with apache version 1.3.19. the question arises when I've tried to run a similar schema on a suse distribution with the same apache version and ��tomcat4.1!!! everything works fine when I startup apache. When I examine the logs of tomcat, I can see the lines wich talk about the connections been established throgh the warpconnector, and the application that WebapDeploy directives refers to is also shown. But, when I try to acces to the directory which should be redirected to tomcat from the apache virtual host, I get errors in both the apache error_log and in the tomcat 4 log. the error in apache log talks about a "segmentation fault" and a child killed, and the error in the tomcat log talks about a broken pipe and a premature end of packet. everything seems like if the apache ends the conexion prematurely because of some kind of mysterious error, and so the tomcat throws an exceptcion talking about it. I suspect that may be caused by the so-recent and nightly version of tomcat (4.1) wich may not be the appropiate one for the mod_webapp.so I'm using (the same I used for the tomcat 4.0), but I have no more clues. Is anybody aut there who has had the same problem? Shall it be caused by the suse dist??? "the truth is somewhere out there". txs. a lot. bye!!!
