--
i've attached some info from www.apache.org - jserv - faq - faq-o-matic -
configuration, to the bottom of this email. None of which worked for me
on my solaris 2.6 sparc5 apache1.3.6 jserv 1.0 setup, by the way, but I'm
far from done investigating.
also, when compiling i get this:
gcc -c -I../../os/unix -I../../include -DSOLARIS2=260 -fPIC
-DSHARED_CORE `../../apaci` -DSHARED_MODULE mod_jserv.c && mv
mod_jserv.o mod_jserv.lo
mod_jserv.c:63: jserv.h: No such file or directory
I've tried going into mod_jserv.c and adding the full path to jserv.h,
which completes the build, but it still doesn't work, i've also added the
path to jserv in the Configuration file, but get the samp problem.
I'm wondering if these are associated, and since that part of the
configuration wasn't mentioned in the installation instructions, i'm
wondering what I could be missing that would cause this kind of error.
Thanks.
-David
Here's the stuff I promised from the faq-o-matic:
(EMERGENCY) ajp11: can not connect to host 127.0.0.1:8007
----------
From: "jon *" <[EMAIL PROTECTED]>
To: Java Apache Users <[EMAIL PROTECTED]>
Date: Fri, Jun 11, 1999, 11:27 AM
> In the mod_jserv.log file, I get :
> (EMERGENCY) ajp11: can not connect to host 127.0.0.1:8007
> (EMERGENCY) ajp11: connection fail
> (ERROR) an error returned handling request via protocol "ajpv11"
That error that you are getting is a result of the JVM not being
able to
start up properly. The error is the mod_jserv C portion of Apache
JServ not
being able to connect to the running Servlet Engine java portion of
the
process.
So, you need to figure out why the JVM is not starting up properly.
Make
sure that all of your paths in all of your configuration files are
correct.
On Win32 machines, this could mean that it is an issue of having
spaces in
your paths. Try setting things up so that there are no spaces
anywhere in
any of your paths. Make sure that the path to the JVM binary
executable is
correct in your jserv.properties file. Make sure that your
wrapper.classpath
has the correct paths to the JSDK and the ApacheJServ.jar file.
-jon
Another thing to look at is the error.log.
Unless the jserv.log file is happy, the jserv engine will throw an
error and write out a stack trace to the error.log.
In my case the problem that stopped the jserv engine from starting
was a problem with the name/access of the jserv.log
file. Even though the log file seems to be specified in both the
jserv.properties and the jserv.conf files, the one that
appears to be important to the start up is the one in
jserv.properties.
I found the *ONE* spot where you'll need to change the configuration
for this particular error:
In httpd.conf, make sure you've put the proper hostname for
ApJServDefaultHost! If Apache, etc. are configured for a
hostname other than "localhost", you've got to make sure JServ can
find the same host.
(This cost me almost two days.)
I managed to solve this problem (which totally prevents JServ from
working on win95) by re-installing both Apache,
and ApacheJserv is directories which didnt have spaces in the full
paths. The standard is "Program Files". Moving both
to "ApacheGroup" appears to have worked quite well.
I had this problem after it had been working fine the day before. I
had not rebooted the machine in the meantime or
anything (Win95+Apache1.3.6+JDK1.2+JServ1.0). I just didn't have the
stomach to do a reinstall yet, so I first made
sure the equivalent 8.3 names were used for all directories/files in
the httpd.conf, mod_jserv.conf, jserv.properties, and
zone.properties files. This seemed to work.
I also lost almost 2 days on this problem. I found that the problem
was caused because I did not configure a full path to
the log file in jserv.properties. [I am using HPUX 10.20, JServ 1.0,
w/ Stronghold]
# Set the name of the trace/log file. To avoid possible confusion
about # the location of this file, an absolute pathname is
recommended. # On Unix, this file must have write permissions by the
owner of the JVM # process. In other words, if you
are running Apache JServ in manual mode # and Apache is running as
user nobody, then the file must have its #
permissions set so that that user can write to it. # Syntax:
log.file=<log file name> (String) # Default: NONE
log.file=/you/must/use/a/full/path/and/it/tells/you/jserv.log
Many thanks to this FAQ for getting me going in the right direction.
On Mon, 12 Jul 1999, Mark Foster wrote:
> --
>
> The output of `netstat -a` would be very helpful in troubleshooting. Also
> you can check `lsof` to see what user/process might be using that port. Mine
> says:
> java 4048 nobody 13u inet 0x06fb3c0c 0t0 TCP *:8007
> (LISTEN)
>
> What port is your web server running (listening) on? Check ALL your logs for
> more clues to why this might be happening.
> -mdf
>
>
>
> -----Original Message-----
> From: Paul Dorn [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 12, 1999 6:36 AM
> To: [EMAIL PROTECTED]
> Subject: Error attaching to auto-started JServ Process
>
>
> I am running the following,
>
> Apache/1.3.6 Ben-SSL/1.35 (Unix) ApacheJServ/1.0 configured
> compiled as DSO. JServ is added via LoadModule
>
> Running on FreeBSD 3.2 RELEASE #0
>
> Everything LOOKS ok, I have several
>
> /usr/local/apache/conf/jserv.properties (java)
>
> processes that start as a result of the web-server starting.
> But i get:
> [12/07/1999 08:18:06:216] (EMERGENCY) ajp11: can not connect to host
> 127.0.0.1:8004
> [12/07/1999 08:18:06:216] (EMERGENCY) ajp11: connection fail
> [12/07/1999 08:18:06:216] (ERROR) an error returned handling request via
> protocol "ajpv11"
> [12/07/1999 08:18:06:216] (ERROR) an error returned handling request via
> protocol "status"
>
> BTW, I get this regardless of where i set JServ and mod_jserv port settings.
> I just changed them to see if I had another process holding 8007.
>
> I have cheched the permissions on the jserv process and the log file.
> I can use the /jserv/ path to talk to mod_jserv but i get the 500
> misconfiguration error if I attempt to reach:
> apjv11://localhost:8007
> or now
> apjv11://localhost:8007
>
> Also, although it is configured, I can not reach the Hello servlet. I get
> the 500 Configuration error
>
>
>
> --
> --------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> READ THE FAQ!!!! <http://java.apache.org/faq/>
> Archives and Other: <http://java.apache.org/main/mail.html/>
> Problems?: [EMAIL PROTECTED]
>
>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
READ THE FAQ!!!! <http://java.apache.org/faq/>
Archives and Other: <http://java.apache.org/main/mail.html/>
Problems?: [EMAIL PROTECTED]