head	1.28;
access;
symbols;
locks
	nobody:1.28; strict;
comment	@# @;


1.28
date	99.10.21.08.49.37;	author nobody;	state Exp;
branches;
next	1.27;

1.27
date	99.10.18.21.42.10;	author nobody;	state Exp;
branches;
next	1.26;

1.26
date	99.10.18.21.40.08;	author nobody;	state Exp;
branches;
next	1.25;

1.25
date	99.10.07.08.00.23;	author nobody;	state Exp;
branches;
next	1.24;

1.24
date	99.10.06.21.05.45;	author nobody;	state Exp;
branches;
next	1.23;

1.23
date	99.10.05.17.37.48;	author nobody;	state Exp;
branches;
next	1.22;

1.22
date	99.10.05.10.03.33;	author nobody;	state Exp;
branches;
next	1.21;

1.21
date	99.10.02.04.27.00;	author nobody;	state Exp;
branches;
next	1.20;

1.20
date	99.10.01.11.28.23;	author nobody;	state Exp;
branches;
next	1.19;

1.19
date	99.09.18.21.54.31;	author nobody;	state Exp;
branches;
next	1.18;

1.18
date	99.08.16.21.27.17;	author nobody;	state Exp;
branches;
next	1.17;

1.17
date	99.08.13.19.36.23;	author nobody;	state Exp;
branches;
next	1.16;

1.16
date	99.08.02.08.31.37;	author nobody;	state Exp;
branches;
next	1.15;

1.15
date	99.08.02.08.30.48;	author nobody;	state Exp;
branches;
next	1.14;

1.14
date	99.07.28.18.50.38;	author nobody;	state Exp;
branches;
next	1.13;

1.13
date	99.07.26.18.35.38;	author nobody;	state Exp;
branches;
next	1.12;

1.12
date	99.07.26.18.35.20;	author nobody;	state Exp;
branches;
next	1.11;

1.11
date	99.07.26.18.26.54;	author nobody;	state Exp;
branches;
next	1.10;

1.10
date	99.07.15.23.15.50;	author nobody;	state Exp;
branches;
next	1.9;

1.9
date	99.07.12.16.16.42;	author nobody;	state Exp;
branches;
next	1.8;

1.8
date	99.07.10.18.56.59;	author nobody;	state Exp;
branches;
next	1.7;

1.7
date	99.06.30.17.02.42;	author nobody;	state Exp;
branches;
next	1.6;

1.6
date	99.06.22.23.07.00;	author nobody;	state Exp;
branches;
next	1.5;

1.5
date	99.06.21.22.18.34;	author nobody;	state Exp;
branches;
next	1.4;

1.4
date	99.06.11.18.36.40;	author nobody;	state Exp;
branches;
next	1.3;

1.3
date	99.06.11.18.36.08;	author nobody;	state Exp;
branches;
next	1.2;

1.2
date	99.06.11.18.35.56;	author nobody;	state Exp;
branches;
next	1.1;

1.1
date	99.06.11.18.35.39;	author nobody;	state Exp;
branches;
next	;


desc
@null
@


1.28
log
@null
@
text
@IDependOn-Set: 1
IDependOn-Set: 2
IDependOn-Set: 216
IDependOn-Set: 222
IDependOn-Set: 263
IDependOn-Set: 7
LastModifiedSecs: 940495776
Parent: 7
SequenceNumber: 22
Title: (EMERGENCY) ajp11: can not connect to host 127.0.0.1:8007, (ERROR) an error returned handling request via protocol "ajpv11"
Part: 0
Author-Set: jon@@working-dogs.com
HideAttributions: 1
LastModifiedSecs: 933014138
Type: monospaced
Lines: 28
----------
From: "jon *" <jon@@clearink.com>
To: Java Apache Users <java-apache-users@@list.working-dogs.com>
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.

Make sure that your permissions are set properly on your log files so that the
userid that the httpd runs under can write to them.

-jon

EndPart: 0
Part: 1
Author-Set: amster@@nanotech.com
HideAttributions: 1
LastModifiedSecs: 930003511
Type: 
Lines: 11
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.

EndPart: 1
Part: 2
Author-Set: egraham@@cobaltgroup.com
HideAttributions: 1
LastModifiedSecs: 930092820
Type: 
Lines: 5
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.)
EndPart: 2
Part: 3
Author-Set: p.lord@@hgmp.mrc.ac.uk
HideAttributions: 1
LastModifiedSecs: 930762161
Type: 
Lines: 5
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. 
EndPart: 3
Part: 4
Author-Set: lyonbf@@ornl.gov
HideAttributions: 1
LastModifiedSecs: 931633019
Type: 
Lines: 1
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.
EndPart: 4
Part: 5
Author-Set: wbunting@@ch.inri.com
HideAttributions: 1
LastModifiedSecs: 931796201
Type: 
Lines: 13
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.
EndPart: 5
Part: 6
Author-Set: dschluss@@instantobjects.com
HideAttributions: 1
LastModifiedSecs: 932080547
Type: 
Lines: 9
Someone way back when set the environment variable JAVA=/usr/java in the .tcshrc file.

This caused both jserv.properties:wrapper.bin to be set to /usr/java and the JAVA variable in all the jserv Makefiles, most notably, the example/Makefile, to be misconfigured.  All makefiles need JAVA set to /usr/bin/java (or wherever your java executable is), likewise with the jserv.properties:wrapper.bin

If you do have to make that change, you will have to re-make both jserv and Hello.  To re-make Hello, go to the example direcotry, fix the JAVA variable, make clean (to remove the old copy), and make.  It would probably be a good idea to re-make all of jserv, but just remaking Hello got me past the (EMERGENCY) error.

-David Schlussel
dschluss@@slip.net

EndPart: 6
Part: 7
Author-Set: brent@@linux1.org
HideAttributions: 1
LastModifiedSecs: 933582697
Type: monospaced
Lines: 11
using blackdown java (1.2pre2) and apache 1.3.6, i found it necessary to set

wrapper.classpath=/path/to/java/jre/lib/rt.jar

(in addition to)
wrapper.classpath=/path/to/jserv/lib/ApacheJServ.jar
wrapper.classpath=/path/to/jsdk/lib/jsdk.jar

in the servlet.properties file. w/o the classpath to rt.jar, the thing
blows up everytime.

EndPart: 7
Part: 8
Author-Set: ggalstia@@head-cfa.harvard.edu
HideAttributions: 1
LastModifiedSecs: 934572982
Type: monospaced
Lines: 8
I've got similar error, on my machine which is using SunOS 5.6 (Solaris 2.6 ).  I was using jdk1.2.1 and was 
getting this message in my error_log  :
----------
You must install a Solaris patch to run this version of the Java runtime.
Please see the README and release notes for more information.
Exiting.
----------
When  I switch from jdk1.2.1 to 1.1.6  everything worked fine.
EndPart: 8
Part: 9
Author-Set: mikea@@actv.com
HideAttributions: 1
LastModifiedSecs: 934838836
Type: monospaced
Lines: 8
If you do specify a "log.file" & make sure it is writable by the running
process, the org.apache.jserv.JServ will not be able to start up and
will not be listening on 8007 for requests. There will be little or no
indication of this state of affairs in the log file, so be careful!

Hint: the first error you will get in this situation is "(EMERGENCY)
ajp11: can not connect to host 127.0.0.1:8007" when you try to hit a
servlet.
EndPart: 9
Part: 10
Author-Set: khoivu@@e-centives.com
HideAttributions: 1
LastModifiedSecs: 937691671
Type: monospaced
Lines: 13
I have tried all things mention here but I still got 
 ajp11: cannot connect ot host 127.0.0.1:8007
Breifly:
my jserv.log is owned by nobody.
I can su to nobody and run jserv manually.
all classpath and path are correct.

What's wrong here.
This is my platform:
Redhat 6.0 with Linux kernel 2.2.5
Apache 1.3.9 and Jserv 1.0
Sunsoft JSDK 2.0

EndPart: 10
Part: 11
Author-Set: pbu@@erlf.siemens.de
HideAttributions: 1
LastModifiedSecs: 938777303
Type: 
Lines: 8
This error message on my Sun using AJ1.0/apache1.3.9/jdk1.1.7 seemed to be the result of configuration-mistakes:

1. The complete-path(!) name to the log-file must be the same in jserv.log and jserv.properties, 
   and the file must be writeable. I changed mode to 777, perhaps this was too much.

2. security.allowedAddresses had to be the real name (not localhost or 127.0.0.0)

After these changes JServ started.
EndPart: 11
Part: 12
Author-Set: sachh@@bigfoot.com
HideAttributions: 1
LastModifiedSecs: 939117812
Type: 
Lines: 16
[05/10/1999 16:47:46:918] (EMERGENCY) ajp11: can not connect to host 127.0.0.1
:8007
[05/10/1999 16:47:46:918] (EMERGENCY) ajp11: connection fail
[05/10/1999 16:47:46:918] (ERROR) an error returned handling request via proto
col "ajpv11"
[05/10/1999 16:47:46:918] (ERROR) an error returned handling request via proto
col "status"
Above error I am getting in my log file after doing all the setup
mentioned in this FAQ.
I am using RH 6.0 with Apache 1.3.6-7 and Jserv 1.0 and JSDK 2.0 and JDK
i had installed through rpm jdk-sn-1.1.6-1.2glibc.
I am able to visit the usr http://localhost/status/jserv
but when i thry to visit url ajpv11:/localhost:8007
it says internal error occured.
where can be the problem?

EndPart: 12
Part: 13
Author-Set: lyonbf@@ornl.gov
LastModifiedSecs: 939243944
Type: 
Lines: 6
Hope this saves someone some time... I just encountered this error again (Linux 2.0.36), and the problem was that the loopback device itself was not configured: JServ couldn't connect to 127.0.0.1:8007 because 127.0.0.1 wasn't reachable (I couldn't even ping it).  I don't know what happened to change this, but the following got it going again:

# Attach the loopback device and add route
/sbin/ifconfig lo 127.0.0.1 
/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo

EndPart: 13
Part: 14
Author-Set: trony@@laoffices.com
LastModifiedSecs: 940282928
Type: html
Lines: 18
same problem for me.<br>
After some try-error, i've put "ApJServLogLevel debug" in jserv.conf , after<br>
that in  mod_jserv.log  appears:<br>

.....
[18/10/1999 22:41:03:011] (INFO) wrapper: Java VM died 5 times in a row with<br> less than 120 seconds between successive failures, setting delay to 60 seconds<br> before restarting. Check the Apache error log and the Apache JServ<br> log files for more details; for maximum log information be sure to<br> enable the Apache  JServ log file in the main jserv properties file by: setting<br> the  'log' property to true, the 'log.file' property to a file<br> writable  by the uid as whom Apache JServ is run, and by enabling log channels <br> using the 'log.channel.*' properties)<br><br>
[18/10/1999 22:41:51:170] (INFO) wrapper: Java VM restarting (PID=5177)<br>
[18/10/1999 22:41:51:172] (INFO) wrapper: Java VM spawned (PID=5215, PPID=5177)<br>
[18/10/1999 22:41:51:174] (INFO) wrapper: Java Virtual Machine unable to start (ERR=2: No such file or directory)<br>
[18/10/1999 22:41:51:174] (ERROR) wrapper: printing debugging information (command line, env)   <br>
.....   <br><br>

The message :(ERR=2: No such file or directory)<br><br>

reminds me to check the executable java path. On rh-6.0 it's /usr/bin/java & not
 /usr/local/java/bin/java  as in the default installed files.<br><br>

After changing the java executable path in jserv.properties, all OK!<br>
EndPart: 14
Part: 15
Author-Set: deepaksharma_98@@yahoo.com
LastModifiedSecs: 940495776
Type: html
Lines: 6
Hello
<p>
I continually received this error until<br>
I changed the version of the JSDK I using.
<p>
Good luck.
EndPart: 15
@


1.27
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 940282928
d9 1
a9 1
SequenceNumber: 21
d274 12
@


1.26
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 940282805
d9 1
a9 1
SequenceNumber: 20
d252 2
a253 1
LastModifiedSecs: 940282805
d255 3
a257 3
same problem for me.
After some try-error, i've put "ApJServLogLevel debug" in jserv.conf , after
that in  mod_jserv.log  appears:
d260 6
a265 6
[18/10/1999 22:41:03:011] (INFO) wrapper: Java VM died 5 times in a row with less than 120 seconds between successive failures, setting delay to 60 seconds before restarting. Check the Apache error log and the Apache JServ log files for more details; for maximum log information be sure to enable the Apache  JServ log file in the main jserv properties file by: setting the  'log' property to true, the 'log.file' property to a file writable  by the uid as whom Apache JServ is run, and by enabling log channels  using the 'log.channel.*' properties)
[18/10/1999 22:41:51:170] (INFO) wrapper: Java VM restarting (PID=5177)
[18/10/1999 22:41:51:172] (INFO) wrapper: Java VM spawned (PID=5215, PPID=5177)
[18/10/1999 22:41:51:174] (INFO) wrapper: Java Virtual Machine unable to start (ERR=2: No such file or directory)
[18/10/1999 22:41:51:174] (ERROR) wrapper: printing debugging information (command line, env)   
.....   
d267 1
a267 1
The message :(ERR=2: No such file or directory)
d270 1
a270 1
 /usr/local/java/bin/java  as in the default installed files.
d272 1
a272 1
After changing the java executable path in jserv.properties, all OK!
@


1.25
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 939243944
d9 1
a9 1
SequenceNumber: 19
d250 23
@


1.24
log
@null
@
text
@d241 1
@


1.23
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 939117812
d9 1
a9 1
SequenceNumber: 18
d238 11
@


1.22
log
@null
@
text
@d219 1
@


1.21
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 938777303
d9 1
a9 1
SequenceNumber: 17
d215 22
@


1.20
log
@null
@
text
@d204 1
@


1.19
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 937691671
d9 1
a9 1
SequenceNumber: 16
d200 14
@


1.18
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 934838836
d9 1
a9 1
SequenceNumber: 15
d180 20
@


1.17
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 934572982
d9 1
a9 1
SequenceNumber: 14
d165 15
@


1.16
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 933582697
d9 1
a9 1
SequenceNumber: 13
d150 15
@


1.15
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 933582647
d9 1
a9 1
SequenceNumber: 12
d135 2
a136 1
LastModifiedSecs: 933582647
@


1.14
log
@null
@
text
@d7 1
a7 1
LastModifiedSecs: 933014138
d9 1
a9 1
SequenceNumber: 11
d132 17
@


1.13
log
@null
@
text
@d5 1
@


1.12
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 933014120
d8 1
a8 1
SequenceNumber: 10
d13 1
a13 1
LastModifiedSecs: 933014119
d15 1
a15 1
Lines: 27
d39 2
a40 1
Make sure that your permissions are set properly on your log files so that the userid that the httpd runs under can write to them.
@


1.11
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 933013613
d8 1
a8 1
SequenceNumber: 9
d13 1
a13 1
LastModifiedSecs: 929126200
d15 1
a15 2
Lines: 26

d38 2
@


1.10
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 932080548
d8 2
a9 2
SequenceNumber: 8
Title: (EMERGENCY) ajp11: can not connect to host 127.0.0.1:8007
d117 1
@


1.9
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 931796201
d8 1
a8 1
SequenceNumber: 7
d97 1
d113 15
@


1.8
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 931633019
d8 1
a8 1
SequenceNumber: 6
d89 1
d93 19
@


1.7
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 930762161
d8 1
a8 1
SequenceNumber: 5
d77 1
d85 7
@


1.6
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 930092820
d8 1
a8 1
SequenceNumber: 4
d65 1
d73 11
@


1.5
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 930003512
d8 1
a8 1
SequenceNumber: 3
d47 1
d61 11
@


1.4
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 929126200
d8 1
a8 1
SequenceNumber: 2
d43 17
@


1.3
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 929126168
d8 1
a8 1
SequenceNumber: 1
d10 33
@


1.2
log
@null
@
text
@d6 1
a6 1
LastModifiedSecs: 929126139
d8 2
a9 2
SequenceNumber: 0
Title: New Item
@


1.1
log
@null
@
text
@d3 1
@
