tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amandeep Jawa" <d...@imagelock.com>
Subject is the FAQ ever up?
Date Tue, 17 Oct 2000 22:56:29 GMT
Is it just me or is the normal tomcat  FAQ-o-matic at
http://jakarta.apache.org/jyve-faq/Turbine/screen/DisplayTopics/action/SetAl
l/project_id/2/faq_id/12

down at least 60% of the time I go to look at it?  what's up w/ that?

aaaarrrrrrrrrrrrrrrrrrrrrgh.

'deep

----- Original Message -----
From: "James Cribb" <JamesC@zoom.com.au>
To: <tomcat-user@jakarta.apache.org>
Cc: <James_Sangroniz@hp.com>
Sent: Tuesday, October 17, 2000 4:36 PM
Subject: RE: trouble connecting apache server to tomcat or jserv


> This was happening to me too at one point, then it stopped so I'm not 100%
> sure about the following:
>
> I believe a bug in mod_jserv.so was crashing httpd.  The bug seemed to be
> triggered by not having any ApJServMount directives in the Apache config
> file.  Unfortunately there is virtually no documentation -- even in the
> source code! -- on what this directive does or why it is needed IN
ADDITION
> TO using SetHandler.
>
> If you have one or more ApJServMount directives in your Apache config file
> and this is still happening, then this theory is wrong.
>
>
>
> -----Original Message-----
> From: James Sangroniz [mailto:James_Sangroniz@hp.com]
> Sent: Wednesday, 18 October 2000 01:32
> To: tomcat-user@jakarta.apache.org
> Subject: trouble connecting apache server to tomcat or jserv
>
>
> I have been trying unsuccessfully for quite a while to get one of the
> Apache servlet engines, (Jserv or Tomcat) to work with an Apache web
> server on a Linux box. The symptom of my difficulty is as follows.
> Hitting a servlet url via browser returns a message stating that the
> document contains no data. None of the jserv or tomcat log files report
> anything. The error log of the apache web server reports the
> following...
> [Fri Oct 13 16:32:54 2000] [notice] child pid 19135 exit signal
> Segmentation fault (11)
>
> [...]
>


Mime
View raw message