You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Denise Mangano <De...@complusdata.com> on 2002/12/15 21:38:37 UTC
RE: Almost there...Updated Apach-Tomcat with mod_jk .. please he
lp!
Jake,
Thanks for supplying me with that info. I will certainly refer to it, when
I set up Tomcat again. However, first I need to get Apache back up and
running. I know this is slightly off topic, but can you tell me how to
check what else is trying to access port 443. Someone suggested that
multiple instances of Apache may be running, but I do not know how to check
this. Nothing else should be accessing this port. I ran netstat and
couldn't believe the stuff that was in it - I have no idea what it is... It
wasn't there a week ago. I tried to attach a file with the netstat output
but get an error message so I will paste below. I am trying desperately to
avoid having to reinstall Apache, because of a third party connector that a
rep came out to install and connect to Apache.
Thanks for looking :)
Denise
netstat output:
Active Internet connections (w/o servers)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 256 192.168.254.87:ssh 192.168.253.5:3082
ESTABLISHED
Active UNIX domain sockets (w/o servers)
Proto RefCnt Flags Type State I-Node Path
unix 10 [ ] DGRAM 929 /dev/log
unix 3 [ ] STREAM CONNECTED 131905
unix 3 [ ] STREAM CONNECTED 131904
unix 3 [ ] STREAM CONNECTED 131903
unix 3 [ ] STREAM CONNECTED 131902
unix 3 [ ] STREAM CONNECTED 2032 /tmp/.famnz0vAN
unix 3 [ ] STREAM CONNECTED 2031
unix 3 [ ] STREAM CONNECTED 2021
/tmp/orbit-root/orb-2142838061391085347
unix 3 [ ] STREAM CONNECTED 2020
unix 3 [ ] STREAM CONNECTED 2016
/tmp/orbit-root/orb-2142838061391085347
unix 3 [ ] STREAM CONNECTED 2014
unix 3 [ ] STREAM CONNECTED 2011
/tmp/orbit-root/orb-536138017165394400
unix 3 [ ] STREAM CONNECTED 2009
unix 3 [ ] STREAM CONNECTED 2008
/tmp/orbit-root/orb-2137805962362223141
unix 3 [ ] STREAM CONNECTED 2006
unix 3 [ ] STREAM CONNECTED 2005
/tmp/orbit-root/orb-12404596331839261261
unix 3 [ ] STREAM CONNECTED 2004
unix 3 [ ] STREAM CONNECTED 2001
/tmp/orbit-root/orb-1562563961725753451
unix 3 [ ] STREAM CONNECTED 2000
unix 3 [ ] STREAM CONNECTED 1999
/tmp/orbit-root/orb-12404596331839261261
unix 3 [ ] STREAM CONNECTED 1997
unix 3 [ ] STREAM CONNECTED 1993
/tmp/orbit-root/orb-1562563961725753451
unix 3 [ ] STREAM CONNECTED 1992
unix 3 [ ] STREAM CONNECTED 1983 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 1982
unix 3 [ ] STREAM CONNECTED 1975 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 1974
unix 3 [ ] STREAM CONNECTED 1941
/tmp/orbit-root/orb-18063637581552786418
unix 3 [ ] STREAM CONNECTED 1940
unix 3 [ ] STREAM CONNECTED 1925
/tmp/orbit-root/orb-4728988062064810212
unix 3 [ ] STREAM CONNECTED 1920
unix 2 [ ] DGRAM 1909
unix 3 [ ] STREAM CONNECTED 1894 /tmp/.ICE-unix/1049
unix 3 [ ] STREAM CONNECTED 1893
unix 3 [ ] STREAM CONNECTED 1890 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 1889
unix 3 [ ] STREAM CONNECTED 1885
/tmp/orbit-root/orb-1562563961725753451
unix 3 [ ] STREAM CONNECTED 1884
unix 3 [ ] STREAM CONNECTED 1874
/tmp/orbit-root/orb-1562563961725753451
unix 3 [ ] STREAM CONNECTED 1872
unix 3 [ ] STREAM CONNECTED 1866 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 1865
unix 2 [ ] DGRAM 1864
unix 3 [ ] STREAM CONNECTED 1853 /tmp/.ICE-unix/1049
unix 3 [ ] STREAM CONNECTED 1852
unix 3 [ ] STREAM CONNECTED 1849 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 1848
unix 3 [ ] STREAM CONNECTED 1839 /tmp/.ICE-unix/1049
unix 3 [ ] STREAM CONNECTED 1838
unix 3 [ ] STREAM CONNECTED 1835 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 1834
unix 3 [ ] STREAM CONNECTED 1769 /tmp/.ICE-unix/1049
unix 3 [ ] STREAM CONNECTED 1768
unix 3 [ ] STREAM CONNECTED 1690 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 1689
unix 3 [ ] STREAM CONNECTED 1659 /tmp/.ICE-unix/1049
unix 3 [ ] STREAM CONNECTED 1658
unix 3 [ ] STREAM CONNECTED 1657 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 1656
unix 3 [ ] STREAM CONNECTED 1643 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 1642
unix 3 [ ] STREAM CONNECTED 1513
/tmp/.font-unix/fs7100
unix 3 [ ] STREAM CONNECTED 1512
unix 4 [ ] STREAM CONNECTED 1515 /tmp/.X11-unix/X0
unix 3 [ ] STREAM CONNECTED 1505
unix 2 [ ] DGRAM 1425
unix 2 [ ] DGRAM 1371
unix 2 [ ] DGRAM 1297
unix 2 [ ] DGRAM 1218
unix 2 [ ] DGRAM 995
unix 2 [ ] DGRAM 938
-----Original Message-----
From: Jacob Kjome
To: Tomcat Users List
Sent: 12/15/2002 12:00 PM
Subject: RE: Almost there...Updated Apach-Tomcat with mod_jk .. please he
lp!
1. Tomcat is so non-intrusive that it is pretty certainly *not* causing
Apache not to work.
2. jk2.properties has *nothing* to do with mod_jk. mod_jk.conf and
workers.properties are the two files you need to worry about.
3. ApacheConfig is a helper to auto-generate mod_jk.conf based on
settings in the web.xml upon Tomcat startup. I has no effect on
anything unless you actually use it in server.xml or run it directly
from the command line.
I'm including a zip file with the contents of my mod_jk config. You'll
have to modify the paths to Unix style (since I am using Win2k), but
otherwise everything should be the same.
All Apache's httpd.conf should have in it is something like this:
Include "C:/Java/Apache/Jakarta/tomcat-4.1.17/conf/jk/mod_jk.conf"
Note that I also included my server.xml. In it, look for <ApacheConfig
...> entries. They are commented out, but should show you how to use
ApacheConfig. I usually use it once and then comment it out. I also
make a copy of the resulting mod_jk.conf, modify it, and use that
instead of directly using the auto-generated one.
Jake
At 02:03 AM 12/15/2002 -0500, you wrote:
At first I thought it might be a permission problem, so I changed
permissions to 775 on workers.properties and still no good. NOW my
Apache
won't work. I am getting an error message saying that Apache could not
bind
to port 443, that the port is already in use. Figuring on the problem
being
Tomcat, I uninstalled Tomcat, and I am still getting the error message
and I
can't bring up my website?! Desperately need to solve that cause my
website,
HAS to be up. Can someone tell me how to check what else is binding to
port
443?
As far as why the jk2.properties, I have no idea! But I can say this,
it
looks like when I built mod_jk it uses a java file called ApacheConfig.
This file has code that points to a different location for mod_jk is
installed then where it actually is on my system. Is it possible that I
need to modify this ApacheConfig file before I build or are my
configuration
settings supposed to override that. (In my error log below you can see
that
it still looks for mod_jk.so in libexec/ even though I changed that
location
in my tomcat config files... That still doesn't explain why even though
its
looking in the right place for my workers.properties file, it says the
file
is not there).
Right now my first problem is more pressing...
THanks!
Denise
-----Original Message-----
From: Milt Epstein
To: Tomcat Users List
Sent: 12/14/2002 11:00 AM
Subject: Re: Almost there...Updated Apach-Tomcat with mod_jk
On Sat, 14 Dec 2002, Denise Mangano wrote:
> I also found this in my cataline.out log.
> INFO: Loading registry information
> Dec 13, 2002 4:29:37 PM org.apache.commons.modeler.Registry
getRegistry
> INFO: Creating new Registry instance
> Dec 13, 2002 4:29:38 PM org.apache.commons.modeler.Registry getServer
> INFO: Creating MBeanServer
> Dec 13, 2002 4:29:39 PM org.apache.coyote.http11.Http11Protocol init
> INFO: Initializing Coyote HTTP/1.1 on port 8080
> mod_jk location: libexec/mod_jk.so
> Make sure it is installed corectly or set the config location
> Using <ApacheConfig modJk="PATH_TO_MOD_JK.SO_OR_DLL" />
> Can't find workers.properties at
> /usr/local/jakarta-tomcat-4.1.17/conf/jk/workers.properties
> Please install it in the default location or set the config location
> Using <ApacheConfig workersConfig="FULL_PATH" />
> Starting service Tomcat-Standalone
> Apache Tomcat/4.1.17
> Dec 13, 2002 4:29:44 PM org.apache.coyote.http11.Http11Protocol start
> INFO: Starting Coyote HTTP/1.1 on port 8080
> Dec 13, 2002 4:29:44 PM org.apache.jk.common.ChannelSocket init
> INFO: JK2: ajp13 listening on /0.0.0.0:8009
> Dec 13, 2002 4:29:44 PM org.apache.jk.server.JkMain start
> INFO: Jk running ID=0 time=2/46
> config=/usr/local/jakarta-tomcat-4.1.17/conf/jk2.properties
>
> It gives me an error that it can't find workers.properties, but it is
in
> fact there...
What is the ownership/permissions on it? In particular, is it
readable by the user Tomcat is running as?
Also, if you're using mod_jk, why all that stuff about jk2?
> -----Original Message-----
> From: Denise Mangano
> To: 'tomcat-user@jakarta.apache.org'
> Sent: 12/13/2002 10:36 PM
> Subject: Almost there...Updated Apach-Tomcat with mod_jk
>
> Here is an update. I managed to get passed the configure fail I was
> getting, and got through the build of mod_jk. I followed everything
to
> the T, and I am back to the almost the same boat that I was in
> yesterday.
>
> Before mod_jk setup I could access http://localhost:8080
<http://localhost:8080/> as well as
> http://localhost. <http://localhost. /> Both apache and Tomacat were
working fine.
Yesterday
>
> after mod_jk install Tomcat stopped working. This time, after second
> try, I can still access both. However, even though I installed mod_jk
I
>
> need to input the :8080.
>
> I restarted apache, and found the following error:
>
> [Fri Dec 13 21:37:08 2002] [error] Error while opening the workers, jk
> will not work
> [Fri Dec 13 21:37:12 2002] [error] (2)No such file or directory: Error
> while opening the workers, jk will not work
>
> Which file is trying to access the workers.properties file that I
> created? I searched the server.xml, the httpd.conf, and the
mod_jk.conf
>
> files and could find nothing that called for it....
>
> As you can see I cannot access the files without using the port :8080
> attached to the end of localhost - if I try to it is still looking in
my
>
> Apache web directory...
>
> [Fri Dec 13 22:04:59 2002] [error] [client 216.164.30.185] File does
not
>
> exist: /var/www/html/examples/jsp/num/numguess.jsp
>
> Any thoughts? I can post my files, if anyone is willing to take a
look
> at it...
>
> Thanks.
> Denise
>
>
> --
> To unsubscribe, e-mail:
> < mailto:tomcat-user-unsubscribe@jakarta.apache.org
<ma...@jakarta.apache.org> >
> For additional commands, e-mail:
> < mailto:tomcat-user-help@jakarta.apache.org
<ma...@jakarta.apache.org> >
>
> --
> To unsubscribe, e-mail:
< mailto:tomcat-user-unsubscribe@jakarta.apache.org
<ma...@jakarta.apache.org> >
> For additional commands, e-mail:
< mailto:tomcat-user-help@jakarta.apache.org
<ma...@jakarta.apache.org> >
>
Milt Epstein
Research Programmer
Integration and Software Engineering (ISE)
Campus Information Technologies and Educational Services (CITES)
University of Illinois at Urbana-Champaign (UIUC)
mepstein@uiuc.edu
--
To unsubscribe, e-mail:
< mailto:tomcat-user-unsubscribe@jakarta.apache.org
<ma...@jakarta.apache.org> >
For additional commands, e-mail:
< mailto:tomcat-user-help@jakarta.apache.org
<ma...@jakarta.apache.org> >
--
To unsubscribe, e-mail: <
mailto:tomcat-user-unsubscribe@jakarta.apache.org
<ma...@jakarta.apache.org> >
For additional commands, e-mail: <
mailto:tomcat-user-help@jakarta.apache.org
<ma...@jakarta.apache.org> >
<<mod_jk_config.zip>> <<ATT03270.txt>>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
RE: Almost there...Updated Apach-Tomcat with mod_jk .. please
he lp!
Posted by micael <ca...@harbornet.com>.
At 03:38 PM 12/15/2002 -0500, you wrote:
>Jake,
>
>Thanks for supplying me with that info. I will certainly refer to it, when
>I set up Tomcat again. However, first I need to get Apache back up and
>running. I know this is slightly off topic, but can you tell me how to
>check what else is trying to access port 443.
Not sure what you meant by "trying to access" but that would not be the
problem, if you mean that literally. Rather, the problem is that some
application is listening at port 443. You have something that is listening
at port 443 for others to access. So, you should have a server set to
listen at 443.
Micael
-------------------------------------------------------
This electronic mail transmission and any accompanying documents contain
information belonging to the sender which may be confidential and legally
privileged. This information is intended only for the use of the
individual or entity to whom this electronic mail transmission was sent as
indicated above. If you are not the intended recipient, any disclosure,
copying, distribution, or action taken in reliance on the contents of the
information contained in this transmission is strictly prohibited. If you
have received this transmission in error, please delete the message. Thank
you
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>