----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files. Don't make us guess your problem!!!
----------------------------------------------------------------
I'm the sysadmin for a group of developers who are all sharing the same
Solaris (2.7) box, and am trying to upgrade Apache 1.3.12 w/Jserv 1.1.1 to
Apache 1.3.12 w/Jserv 1.1.2. This is a box with multiple Apache
installations running, all binding to separate interfaces. Because we have
so many developers, I have to maintain several completely separate
environments by binding separate Apaches to separate ip's -- I can't create
virtual servers or anything like that.
After installing, I make the following three changes to my config files:
1. In httpd.conf, I add a line like this:
Include /usr/local/www/momo.dev.sonatainc.com/jserv/etc/jserv.conf
I also bind Apache to a specific IP:
BindAddress 192.168.134.5
2. In jserv.conf:
ApJServDefaultHost 192.168.134.5
3. In jserv.properties:
bindaddress=192.168.134.5
Upon startup, I get the following errors:
1. In jserv_log:
[14/08/2000 17:38:04:164 EDT] Connections from momo/192.168.134.5 are not
allowed
2. And then in jserv.properties, there's the old favorite:
[14/08/2000 17:38:15:158] (EMERGENCY) ajp12: ping: no reply (-1) Please make
sure that the wrapper.classpath is pointing to the correct version of
ApacheJServ.jar
I've made NO other changes to these files -- the path to ApacheJServ.jar IS
correct!
# grep classpath *
[...snip...]
jserv.properties:wrapper.classpath=/usr/local/www/momo.dev.sonatainc.com/jse
rv/libexec/ApacheJServ.jar
jserv.properties:wrapper.classpath=/usr/local/java/jsdk/lib/jsdk.jar
[...snip...]
# ls -l /usr/local/www/momo.dev.sonatainc.com/jserv/libexec/ApacheJServ.jar
-rw-r--r-- 1 www dev 86875 Aug 14 16:35
/usr/local/www/momo.dev.sonatainc.com/jserv/libexec/ApacheJServ.jar
# ls -l /usr/local/java/jsdk/lib/jsdk.jar
-r--r--r-- 1 nobody nobody 76453 Apr 21 1998
/usr/local/java/jsdk/lib/jsdk.jar
#
In fact, when I forgo attempting to bing Jserv to any particular IP (ie, I
don't make changes 2 and 3), it works just fine. The thing is, though, I
*have* to figure out a way to make it bind to a particular IP, or the
developers will be stepping on one another's toes as they stop and restart
their respective webservers.
I think the answer lies in the "Connections from momo/192.168.134.5 are not
allowed" message; however, I couldn't find anything in the documentation
about this (which doesn't mean that it's not there, of course). Is there
some new security feature I need to configure? I'll also note that I never
ran into this problem before attempting this upgrade.
Can anyone shed some light on this problem? Or at least point me in the
direction of the documentation that does?
Thanks very much
Elizabeth Genco
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search Archives:
<http://www.mail-archive.com/java-apache-users%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
