tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Turner, John" <JTur...@AAS.com>
Subject RE: problems compiling and using mod_jk
Date Wed, 26 Feb 2003 19:44:43 GMT

Just comment out the ManagedBean elements in server.xml.  That will get rid
of those error messages, they are not compatible with Ajp13Connector.

John


> -----Original Message-----
> From: Mike Jackson [mailto:mjackson@cdi-hq.com]
> Sent: Wednesday, February 26, 2003 2:40 PM
> To: Tomcat Users List
> Subject: RE: problems compiling and using mod_jk
> 
> 
> Ok, I've got mod_jk to compile and work with apache 1.3.27 
> and tomcat 3.3.x.
> However I can't get it to work with tomcat 4.1.18.  The 
> module loads, but it
> doesn't seem like it can talk to tomcat.  I tried to change 
> the server.xml
> file to use the older apj13 connector, but it fails to load, gets a
> java.lang.Exception: ManagedBean is not found with Ajp13Connector.
> 
> So my question is, where to go, should I switch back to the 
> coyote connector
> and try to get it working?  Or is there something I can do to fix that
> ManagedBean exception?
> 
> --mikej
> -=-----
> mike jackson
> mjackson@cdi-hq.com
> 
> > -----Original Message-----
> > From: Turner, John [mailto:JTurner@AAS.com]
> > Sent: Wednesday, February 26, 2003 11:04 AM
> > To: 'Tomcat Users List'
> > Subject: RE: problems compiling and using mod_jk
> >
> >
> >
> > Sounds good to me, I really have no idea.  My experience with
> > build tools is
> > pretty minimal.
> >
> > John
> >
> > > -----Original Message-----
> > > From: Mike Jackson [mailto:mjackson@cdi-hq.com]
> > > Sent: Wednesday, February 26, 2003 2:02 PM
> > > To: Tomcat Users List
> > > Subject: RE: problems compiling and using mod_jk
> > >
> > >
> > > I found an install-sh in
> > > "/usr/local/share/automake/install-sh", is that
> > > where it ought to get getting it from?
> > >
> > > --mikej
> > > -=-----
> > > mike jackson
> > > mjackson@cdi-hq.com
> > >
> > > > -----Original Message-----
> > > > From: Mike Jackson [mailto:mjackson@cdi-hq.com]
> > > > Sent: Wednesday, February 26, 2003 10:59 AM
> > > > To: Tomcat Users List
> > > > Subject: RE: problems compiling and using mod_jk
> > > >
> > > >
> > > > It looks like there's an ac_aux_dir that isn't begin set
> > > properly, where
> > > > does that come from and what should it look like?  The 
> ac_aux_dir is
> > > > referenced in aclocal.m4.  It says "Actually configure libtool.
> > > > ac_aux_dir
> > > > is where install-sh is found." in a comment in the area I
> > > think that the
> > > > problem might be at, but I can't seem to figure out what it
> > > should be and
> > > > where it ought to be set.
> > > >
> > > > --mikej
> > > > -=-----
> > > > mike jackson
> > > > mjackson@cdi-hq.com
> > > >
> > > > > -----Original Message-----
> > > > > From: Mike Jackson [mailto:mjackson@cdi-hq.com]
> > > > > Sent: Wednesday, February 26, 2003 10:46 AM
> > > > > To: Tomcat Users List
> > > > > Subject: RE: problems compiling and using mod_jk
> > > > >
> > > > >
> > > > > I'm root, I don't see how there could be a 
> permissions problem. :)
> > > > >
> > > > > --mikej
> > > > > -=-----
> > > > > mike jackson
> > > > > mjackson@cdi-hq.com
> > > > >
> > > > > > -----Original Message-----
> > > > > > From: Turner, John [mailto:JTurner@AAS.com]
> > > > > > Sent: Wednesday, February 26, 2003 10:34 AM
> > > > > > To: 'Tomcat Users List'
> > > > > > Subject: RE: problems compiling and using mod_jk
> > > > > >
> > > > > >
> > > > > >
> > > > > > I would say "Yes". ;)
> > > > > >
> > > > > > Could it be a permissions problem?  There aren't 
> many reasons
> > > > > for a failed
> > > > > > copy.
> > > > > >
> > > > > > John
> > > > > >
> > > > > > > -----Original Message-----
> > > > > > > From: Mike Jackson [mailto:mjackson@cdi-hq.com]
> > > > > > > Sent: Wednesday, February 26, 2003 1:26 PM
> > > > > > > To: Tomcat Users List
> > > > > > > Subject: RE: problems compiling and using mod_jk
> > > > > > >
> > > > > > >
> > > > > > > Ok I've got the latest versions (again), removed any
> > > > > > > lingering build and
> > > > > > > installed files, and unpacked the srcs and 
> binaries (tomcat
> > > > > > > is binary).
> > > > > > > Apache2 seems to have compiled and installed 
> successfully.  I
> > > > > > > haven't tried
> > > > > > > to start it yet, but I'll do that after I get the 
> connector
> > > > > > > built.  Anyway,
> > > > > > > I ran buildconf.sh and got the following:
> > > > > > >
> > > > > > > # ./buildconf.sh
> > > > > > > libtoolize --force --automake --copy
> > > > > > > aclocal
> > > > > > > automake -a --foreign -i --copy
> > > > > > > automake: configure.in: installing
> > > `scripts/build/unix/install-sh'
> > > > > > >     error while copying
> > > > > > >
> > > > > > > automake: configure.in: installing
> > > > `scripts/build/unix/mkinstalldirs'
> > > > > > >     error while copying
> > > > > > >
> > > > > > > automake: configure.in: installing
> > > `scripts/build/unix/missing'
> > > > > > >     error while copying
> > > > > > >
> > > > > > > autoconf
> > > > > > >
> > > > > > > Do I already have a problem?
> > > > > > >
> > > > > > > --mikej
> > > > > > > -=-----
> > > > > > > mike jackson
> > > > > > > mjackson@cdi-hq.com
> > > > > > >
> > > > > > > > -----Original Message-----
> > > > > > > > From: Mike Jackson [mailto:mjackson@cdi-hq.com]
> > > > > > > > Sent: Wednesday, February 26, 2003 10:08 AM
> > > > > > > > To: Tomcat Users List
> > > > > > > > Subject: RE: problems compiling and using mod_jk
> > > > > > > >
> > > > > > > >
> > > > > > > > Hmm, ok, then:
> > > > > > > >
> > > > > > > > # find / -name apxs -print
> > > > > > > > /home/mjackson/new-apache/httpd-2.0.44/support/apxs
> > > > > > > >
> > > > > > > > 	the build directory for apache2
> > > > > > > >
> > > > > > > > /usr/local/apache/bin/apxs
> > > > > > > >
> > > > > > > > 	the apache 1.3 install
> > > > > > > >
> > > > > > > > /usr/local/apache2/bin/apxs
> > > > > > > >
> > > > > > > > 	the apache 2.0.44 install
> > > > > > > >
> > > > > > > > I didn't find any others out there.  I'll remove and
> > > > > > > re-setup the apache
> > > > > > > > install.  I run some "production" code on the 
> old version
> > > > > > > of apache (with
> > > > > > > > tomcat 3.3.1a), but I can remove it temporarily and
> > > see if that
> > > > > > > > helps.  I'll
> > > > > > > > just go some "fresh" archives for the source again.
> > > > > > > >
> > > > > > > > --mikej
> > > > > > > > -=-----
> > > > > > > > mike jackson
> > > > > > > > mjackson@cdi-hq.com
> > > > > > > >
> > > > > > > > > -----Original Message-----
> > > > > > > > > From: Jake Robb [mailto:jakerobb@mac.com]
> > > > > > > > > Sent: Wednesday, February 26, 2003 9:59 AM
> > > > > > > > > To: Tomcat Users List
> > > > > > > > > Subject: Re: problems compiling and using mod_jk
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > I had a similar problem trying to build mod_jk2,
> > > where it didn't
> > > > > > > > > create the
> > > > > > > > > .so file.
> > > > > > > > >
> > > > > > > > > I don't remember it very well, but I believe 
> the problem
> > > > > > > was that I had
> > > > > > > > > upgraded Apache, but had missed the copy of apxs
> > > in /usr/bin.
> > > > > > > > By removing
> > > > > > > > > /usr/bin/apxs and /usr/bin/apachectl, plus my
> > > entire Apache2
> > > > > > > > installation,
> > > > > > > > > and then rebuilding from source, I was able to rebuild
> > > > > > > apxs, which then
> > > > > > > > > solved the problem.
> > > > > > > > >
> > > > > > > > > John: by the way, the --with-apxs2 argument is
> > > only for jk2.
> > > > > > > > >
> > > > > > > > > Mike: the "no apache given" message is okay.  
> The script
> > > > > > > looks for both
> > > > > > > > > apache and apache2 (you could specify both, if
> > > for whatever
> > > > > > > > > reason you have
> > > > > > > > > both installed).  It didn't find a 1.3.x version
> > > of Apache, and
> > > > > > > > > that's not a
> > > > > > > > > problem.
> > > > > > > > >
> > > > > > > > > -Jake
> > > > > > > > >
> > > > > > > > > ----- Original Message -----
> > > > > > > > > From: "Mike Jackson" <mjackson@cdi-hq.com>
> > > > > > > > > To: "Tomcat Users List" 
> <tomcat-user@jakarta.apache.org>
> > > > > > > > > Sent: Wednesday, February 26, 2003 12:20 PM
> > > > > > > > > Subject: RE: problems compiling and using mod_jk
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > I didn't get the configure AC_PROG_CPP error,
> > > but here's what
> > > > > > > > was output
> > > > > > > > > in
> > > > > > > > > > apache-2.0
> > > > > > > > > >
> > > > > > > > > > # ls -l
> > > > > > > > > > total 3462
> > > > > > > > > > -rw-r--r--    1 root     sys            2243 Feb 26
> > > > > > > 09:19 Makefile
> > > > > > > > > > -rw-r--r--    1 root     sys             736
> > > Feb 26 09:19
> > > > > > > > Makefile.apxs
> > > > > > > > > > -rw-r--r--    1 root     root            661
> > > Dec 19 05:52
> > > > > > > > > Makefile.apxs.in
> > > > > > > > > > -rw-r--r--    1 root     root           2131 Dec 19
> > > > > > > 05:52 Makefile.in
> > > > > > > > > > -rw-r--r--    1 root     root          15020 Dec 19
> > > > > > > 05:52 bldjk.qclsrc
> > > > > > > > > > -rw-r--r--    1 root     root            448 Dec 19
> > > > > > > 05:52 config.m4
> > > > > > > > > > -rw-r--r--    1 root     sys          777044 Feb 26
> > > > > > > 09:20 libmod_jk.a
> > > > > > > > > > lrwxrwxrwx    1 root     sys              18
> > > Feb 26 09:20
> > > > > > > > > libmod_jk.so ->
> > > > > > > > > > libmod_jk.so.0.0.0
> > > > > > > > > > lrwxrwxrwx    1 root     sys              18
> > > Feb 26 09:20
> > > > > > > > > libmod_jk.so.0 ->
> > > > > > > > > > libmod_jk.so.0.0.0
> > > > > > > > > > -rw-r--r--    1 root     sys          689252
> > > Feb 26 09:20
> > > > > > > > > libmod_jk.so.0.0.0
> > > > > > > > > > -rw-r--r--    1 root     root          70552 Dec 19
> > > > > > > 05:52 mod_jk.c
> > > > > > > > > > -rw-r--r--    1 root     root           7129 Dec 19
> > > > > > > 05:52 mod_jk.dsp
> > > > > > > > > > -rw-r--r--    1 root     sys             729 Feb 26
> > > > > > > 09:20 mod_jk.la
> > > > > > > > > > -rw-r--r--    1 root     sys          102128 Feb 26
> > > > > > > 09:20 mod_jk.lo
> > > > > > > > > > -rw-r--r--    1 root     sys           98392 Feb 26
> > > > > > > 09:20 mod_jk.o
> > > > > > > > > >
> > > > > > > > > > I've got a mod_jk.o, but that's not the 
> correct file.
> > > >  It looks
> > > > > > > > > to me like
> > > > > > > > > > the right one should be libmod_jk.so.0.0.0, 
> but I could
> > > > > > > be mistaken.
> > > > > > > > > >
> > > > > > > > > > --mikej
> > > > > > > > > > -=-----
> > > > > > > > > > mike jackson
> > > > > > > > > > mjackson@cdi-hq.com
> > > > > > > > > >
> > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > From: Turner, John [mailto:JTurner@AAS.com]
> > > > > > > > > > > Sent: Wednesday, February 26, 2003 9:15 AM
> > > > > > > > > > > To: 'Tomcat Users List'
> > > > > > > > > > > Subject: RE: problems compiling and using mod_jk
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > buildconf.sh told me this:
> > > > > > > > > > >
> > > > > > > > > > > libtoolize --force --automake --copy
> > > > > > > > > > > aclocal
> > > > > > > > > > > automake -a --foreign -i --copy
> > > > > > > > > > > autoconf
> > > > > > > > > > > configure.in:24: AC_PROG_CPP was called
> > > before AC_PROG_CC
> > > > > > > > > > >
> > > > > > > > > > > Then I ran: ./configure
> > > > > > > --with-apxs=/usr/local/apache2/bin/apxs
> > > > > > > > > > >
> > > > > > > > > > > Everything went OK, then I ran make.
> > > Everything went OK,
> > > > > > > > > with the final
> > > > > > > > > > > result being:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > >
> > > /usr/local/src/jakarta-tomcat-connectors-jk-1.2.2-src/jk/native/ap
> > > > > > > > > > > ache-2.0/.
> > > > > > > > > > > libs/mod_jk.so
> > > > > > > > > > >
> > > > > > >
> > > /usr/local/src/jakarta-tomcat-connectors-jk-1.2.2-src/jk/native/ap
> > > > > > > > > > > ache-2.0/m
> > > > > > > > > > > od_jk.so
> > > > > > > > > > >
> > > > > > > > > > > John
> > > > > > > > > > >
> > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > From: Mike Jackson [mailto:mjackson@cdi-hq.com]
> > > > > > > > > > > > Sent: Wednesday, February 26, 2003 12:09 PM
> > > > > > > > > > > > To: Tomcat Users List
> > > > > > > > > > > > Subject: RE: problems compiling and using mod_jk
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > > I tried that, here's the output.  For 
> some reason it
> > > > > > > > can't find the
> > > > > > > > > > > > webserver.  I was playing with the version
> > > in "native2",
> > > > > > > > it required
> > > > > > > > > > > > the --with-apxs2 option, but I haven't got
> > > that one to
> > > > > > > > > > > > compile yet, I'm
> > > > > > > > > > > > getting make errors.
> > > > > > > > > > > >
> > > > > > > > > > > > Configure output...
> > > > > > > > > > > >
> > > > > > > 
> --------------------------------------------------------------
> > > > > > > > > > > > --------------
> > > > > > > > > > > > ---------------
> > > > > > > > > > > > # ./configure
> > > --with-apxs2=/usr/local/apache2/bin/apxs
> > > > > > > > > > > > loading cache ./config.cache
> > > > > > > > > > > > checking for a BSD compatible install...
> > > > > > > > > > > > scripts/build/unix/install-sh -c
> > > > > > > > > > > > checking whether build environment is 
> sane... yes
> > > > > > > > > > > > checking whether make sets ${MAKE}... 
> (cached) yes
> > > > > > > > > > > > checking for working aclocal... found
> > > > > > > > > > > > checking for working autoconf... found
> > > > > > > > > > > > checking for working automake... found
> > > > > > > > > > > > checking for working autoheader... found
> > > > > > > > > > > > checking for working makeinfo... missing
> > > > > > > > > > > > checking host system type... 
> i586-sco-sysv5uw7.1.1
> > > > > > > > > > > > checking build system type... 
> i586-sco-sysv5uw7.1.1
> > > > > > > > > > > > checking for ranlib... (cached) :
> > > > > > > > > > > > checking for gcc... (cached) gcc
> > > > > > > > > > > > checking whether the C compiler (gcc  ) 
> works... yes
> > > > > > > > > > > > checking whether the C compiler (gcc  ) is a
> > > > > > > cross-compiler... no
> > > > > > > > > > > > checking whether we are using GNU C... 
> (cached) yes
> > > > > > > > > > > > checking whether gcc accepts -g... (cached) yes
> > > > > > > > > > > > checking for ld used by GCC... (cached)
> > > /usr/ccs/bin/ld
> > > > > > > > > > > > checking if the linker (/usr/ccs/bin/ld) is GNU
> > > > > > > ld... (cached) no
> > > > > > > > > > > > checking for BSD-compatible nm... (cached)
> > > /usr/bin/nm -p
> > > > > > > > > > > > checking whether ln -s works... (cached) yes
> > > > > > > > > > > > loading cache ./config.cache within ltconfig
> > > > > > > > > > > > checking for object suffix... o
> > > > > > > > > > > > checking for executable suffix... (cached) no
> > > > > > > > > > > > checking for gcc option to produce PIC... -fPIC
> > > > > > > > > > > > checking if gcc PIC flag -fPIC works... yes
> > > > > > > > > > > > checking if gcc supports -c -o file.o... yes
> > > > > > > > > > > > checking if gcc supports -c -o file.lo... yes
> > > > > > > > > > > > checking if gcc supports -fno-rtti
> > > -fno-exceptions ... yes
> > > > > > > > > > > > checking if gcc static flag -static 
> works... -static
> > > > > > > > > > > > checking if the linker (/usr/ccs/bin/ld) is
> > > GNU ld... no
> > > > > > > > > > > > checking whether the linker (/usr/ccs/bin/ld)
> > > > > > > supports shared
> > > > > > > > > > > > libraries...
> > > > > > > > > > > > yes
> > > > > > > > > > > > checking command to parse /usr/bin/nm -p
> > > output... ok
> > > > > > > > > > > > checking how to hardcode library paths into
> > > > > > > programs... immediate
> > > > > > > > > > > > checking for /usr/ccs/bin/ld option to reload
> > > > > > > object files... -r
> > > > > > > > > > > > checking dynamic linker characteristics...
> > > > > > > sysv5uw7.1.1 ld.so
> > > > > > > > > > > > checking if libtool supports shared 
> libraries... yes
> > > > > > > > > > > > checking whether to build shared 
> libraries... yes
> > > > > > > > > > > > checking whether to build static 
> libraries... yes
> > > > > > > > > > > > checking for objdir... .libs
> > > > > > > > > > > > checking for dlfcn.h... (cached) yes
> > > > > > > > > > > > checking whether a program can dlopen itself...
> > > > (cached) no
> > > > > > > > > > > > creating libtool
> > > > > > > > > > > > loading cache ./config.cache
> > > > > > > > > > > > checking for gcc... (cached) gcc
> > > > > > > > > > > > checking whether the C compiler (gcc -g -O2
> > > ) works... yes
> > > > > > > > > > > > checking whether the C compiler (gcc -g 
> -O2 ) is a
> > > > > > > > > > > > cross-compiler... no
> > > > > > > > > > > > checking whether we are using GNU C... 
> (cached) yes
> > > > > > > > > > > > checking whether gcc accepts -g... (cached) yes
> > > > > > > > > > > > checking for ld used by GCC... (cached)
> > > /usr/ccs/bin/ld
> > > > > > > > > > > > checking if the linker (/usr/ccs/bin/ld) is GNU
> > > > > > > ld... (cached) no
> > > > > > > > > > > > checking for test... (cached) /usr/bin/test
> > > > > > > > > > > > checking for rm... (cached) /sbin/rm
> > > > > > > > > > > > checking for grep... (cached) /sbin/grep
> > > > > > > > > > > > checking for echo... (cached) 
> /usr/local/bin/echo
> > > > > > > > > > > > checking for sed... (cached) /usr/bin/sed
> > > > > > > > > > > > checking for cp... (cached) /sbin/cp
> > > > > > > > > > > > checking for mkdir... (cached) /usr/bin/mkdir
> > > > > > > > > > > > checking for libtool... (cached)
> > > /usr/local/bin/libtool
> > > > > > > > > > > > no apxs given
> > > > > > > > > > > > checking for target platform... unix
> > > > > > > > > > > > no apache given
> > > > > > > > > > > > configure: error: Cannot find the WebServer
> > > > > > > > > > > >
> > > > > > > 
> --------------------------------------------------------------
> > > > > > > > > > > > --------------
> > > > > > > > > > > > ---------------
> > > > > > > > > > > >
> > > > > > > > > > > > --mikej
> > > > > > > > > > > > -=-----
> > > > > > > > > > > > mike jackson
> > > > > > > > > > > > mjackson@cdi-hq.com
> > > > > > > > > > > >
> > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > From: Turner, John [mailto:JTurner@AAS.com]
> > > > > > > > > > > > > Sent: Wednesday, February 26, 2003 9:02 AM
> > > > > > > > > > > > > To: 'Tomcat Users List'
> > > > > > > > > > > > > Subject: RE: problems compiling and 
> using mod_jk
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > I think the culprit is the --with-apxs option,
> > > > now that I
> > > > > > > > > > > > think about it.
> > > > > > > > > > > > >
> > > > > > > > > > > > > Apache 1.3: 
> --with-apxs=/path/to/apache/bin/apxs
> > > > > > > > > > > > >
> > > > > > > > > > > > > Apache 2.0: 
> --with-apxs2=/path/to/apache2/bin/apxs
> > > > > > > > > > > > >
> > > > > > > > > > > > > I'm going to try it right now on RH 7.2 for
> > > > apache 2.0 and
> > > > > > > > > > > > see what's
> > > > > > > > > > > > > what...its been several weeks since I did it
> > > > and I need a
> > > > > > > > > refresher.
> > > > > > > > > > > > >
> > > > > > > > > > > > > John
> > > > > > > > > > > > >
> > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > From: Mike Jackson 
> [mailto:mjackson@cdi-hq.com]
> > > > > > > > > > > > > > Sent: Wednesday, February 26, 2003 11:53 AM
> > > > > > > > > > > > > > To: Tomcat Users List
> > > > > > > > > > > > > > Subject: RE: problems compiling and 
> using mod_jk
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > I don't see anything in particular, 
> but I might
> > > > > > > be missing
> > > > > > > > > > > > > > something.  The
> > > > > > > > > > > > > > only thing that looked worrisome was the "no
> > > > > > > apache given"
> > > > > > > > > > > > > > message output
> > > > > > > > > > > > > > from the configure script.  But maybe one of
> > > > > > > you folks will
> > > > > > > > > > > > > > have a clue that
> > > > > > > > > > > > > > I don't.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Here's the output from ./configure
> > > > > > > > > > > > > > --with-apxs=/usr/local/apache2/bin/apxs
> > > > > > > > > > > > > >
> > > > > > > 
> --------------------------------------------------------------
> > > > > > > > > > > > > > --------------
> > > > > > > > > > > > > > ----------------
> > > > > > > > > > > > > > # ./configure
> > > --with-apxs=/usr/local/apache2/bin/apxs
> > > > > > > > > > > > > > loading cache ./config.cache
> > > > > > > > > > > > > > checking for a BSD compatible install...
> > > > > > > > > > > > > > scripts/build/unix/install-sh -c
> > > > > > > > > > > > > > checking whether build environment is
> > > sane... yes
> > > > > > > > > > > > > > checking whether make sets ${MAKE}...
> > > (cached) yes
> > > > > > > > > > > > > > checking for working aclocal... found
> > > > > > > > > > > > > > checking for working autoconf... found
> > > > > > > > > > > > > > checking for working automake... found
> > > > > > > > > > > > > > checking for working autoheader... found
> > > > > > > > > > > > > > checking for working makeinfo... missing
> > > > > > > > > > > > > > checking host system type...
> > > i586-sco-sysv5uw7.1.1
> > > > > > > > > > > > > > checking build system type...
> > > i586-sco-sysv5uw7.1.1
> > > > > > > > > > > > > > checking for ranlib... (cached) :
> > > > > > > > > > > > > > checking for gcc... (cached) gcc
> > > > > > > > > > > > > > checking whether the C compiler (gcc  )
> > > works... yes
> > > > > > > > > > > > > > checking whether the C compiler (gcc  ) is a
> > > > > > > > > cross-compiler... no
> > > > > > > > > > > > > > checking whether we are using GNU C...
> > > (cached) yes
> > > > > > > > > > > > > > checking whether gcc accepts -g... 
> (cached) yes
> > > > > > > > > > > > > > checking for ld used by GCC... (cached)
> > > > /usr/ccs/bin/ld
> > > > > > > > > > > > > > checking if the linker
> > > (/usr/ccs/bin/ld) is GNU ld...
> > > > > > > > > (cached) no
> > > > > > > > > > > > > > checking for BSD-compatible nm... (cached)
> > > > > > > /usr/bin/nm -p
> > > > > > > > > > > > > > checking whether ln -s works... (cached) yes
> > > > > > > > > > > > > > loading cache ./config.cache within ltconfig
> > > > > > > > > > > > > > checking for object suffix... o
> > > > > > > > > > > > > > checking for executable suffix... 
> (cached) no
> > > > > > > > > > > > > > checking for gcc option to produce 
> PIC... -fPIC
> > > > > > > > > > > > > > checking if gcc PIC flag -fPIC works... yes
> > > > > > > > > > > > > > checking if gcc supports -c -o file.o... yes
> > > > > > > > > > > > > > checking if gcc supports -c -o 
> file.lo... yes
> > > > > > > > > > > > > > checking if gcc supports -fno-rtti
> > > > > > > -fno-exceptions ... yes
> > > > > > > > > > > > > > checking if gcc static flag -static
> > > works... -static
> > > > > > > > > > > > > > checking if the linker (/usr/ccs/bin/ld) is
> > > > GNU ld... no
> > > > > > > > > > > > > > checking whether the linker 
> (/usr/ccs/bin/ld)
> > > > > > > supports shared
> > > > > > > > > > > > > > libraries...
> > > > > > > > > > > > > > yes
> > > > > > > > > > > > > > checking command to parse /usr/bin/nm
> > > -p output... ok
> > > > > > > > > > > > > > checking how to hardcode library paths into
> > > > programs...
> > > > > > > > > immediate
> > > > > > > > > > > > > > checking for /usr/ccs/bin/ld option to
> > > reload object
> > > > > > > > files... -r
> > > > > > > > > > > > > > checking dynamic linker characteristics...
> > > > > > > sysv5uw7.1.1 ld.so
> > > > > > > > > > > > > > checking if libtool supports shared
> > > libraries... yes
> > > > > > > > > > > > > > checking whether to build shared
> > > libraries... yes
> > > > > > > > > > > > > > checking whether to build static
> > > libraries... yes
> > > > > > > > > > > > > > checking for objdir... .libs
> > > > > > > > > > > > > > checking for dlfcn.h... (cached) yes
> > > > > > > > > > > > > > checking whether a program can 
> dlopen itself...
> > > > > > > (cached) no
> > > > > > > > > > > > > > creating libtool
> > > > > > > > > > > > > > loading cache ./config.cache
> > > > > > > > > > > > > > checking for gcc... (cached) gcc
> > > > > > > > > > > > > > checking whether the C compiler 
> (gcc -g -O2 )
> > > > > > > works... yes
> > > > > > > > > > > > > > checking whether the C compiler (gcc -g
> > > -O2 ) is a
> > > > > > > > > > > > > > cross-compiler... no
> > > > > > > > > > > > > > checking whether we are using GNU C...
> > > (cached) yes
> > > > > > > > > > > > > > checking whether gcc accepts -g... 
> (cached) yes
> > > > > > > > > > > > > > checking for ld used by GCC... (cached)
> > > > /usr/ccs/bin/ld
> > > > > > > > > > > > > > checking if the linker
> > > (/usr/ccs/bin/ld) is GNU ld...
> > > > > > > > > (cached) no
> > > > > > > > > > > > > > checking for test... (cached) /usr/bin/test
> > > > > > > > > > > > > > checking for rm... (cached) /sbin/rm
> > > > > > > > > > > > > > checking for grep... (cached) /sbin/grep
> > > > > > > > > > > > > > checking for echo... (cached)
> > > /usr/local/bin/echo
> > > > > > > > > > > > > > checking for sed... (cached) /usr/bin/sed
> > > > > > > > > > > > > > checking for cp... (cached) /sbin/cp
> > > > > > > > > > > > > > checking for mkdir... (cached) 
> /usr/bin/mkdir
> > > > > > > > > > > > > > checking for libtool... (cached)
> > > > /usr/local/bin/libtool
> > > > > > > > > > > > > > need to check for Perl first, apxs
> > > depends on it...
> > > > > > > > > > > > > > checking for perl... (cached)
> > > /usr/local/bin/perl
> > > > > > > > > > > > > > building connector for "apache-2.0"
> > > > > > > > > > > > > > checking for target platform... unix
> > > > > > > > > > > > > > no apache given
> > > > > > > > > > > > > > creating ./config.status
> > > > > > > > > > > > > > creating Makefile
> > > > > > > > > > > > > > creating apache-1.3/Makefile
> > > > > > > > > > > > > > creating apache-1.3/Makefile.apxs
> > > > > > > > > > > > > > creating apache-2.0/Makefile
> > > > > > > > > > > > > > creating apache-2.0/Makefile.apxs
> > > > > > > > > > > > > > creating common/Makefile
> > > > > > > > > > > > > > creating common/list.mk
> > > > > > > > > > > > > > creating jni/Makefile
> > > > > > > > > > > > > >
> > > > > > > 
> --------------------------------------------------------------
> > > > > > > > > > > > > > --------------
> > > > > > > > > > > > > > ----------------
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > And here's config.log
> > > > > > > > > > > > > >
> > > > > > > 
> --------------------------------------------------------------
> > > > > > > > > > > > > > --------------
> > > > > > > > > > > > > > ----------------
> > > > > > > > > > > > > > This file contains any messages produced by
> > > > > > > compilers while
> > > > > > > > > > > > > > running configure, to aid debugging if
> > > configure makes
> > > > > > > > > a mistake.
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > configure:694: checking for a BSD
> > > compatible install
> > > > > > > > > > > > > > configure:747: checking whether build
> > > > > > > environment is sane
> > > > > > > > > > > > > > configure:804: checking whether make
> > > sets ${MAKE}
> > > > > > > > > > > > > > configure:850: checking for working aclocal
> > > > > > > > > > > > > > configure:863: checking for working autoconf
> > > > > > > > > > > > > > configure:876: checking for working automake
> > > > > > > > > > > > > > configure:889: checking for working 
> autoheader
> > > > > > > > > > > > > > configure:902: checking for working makeinfo
> > > > > > > > > > > > > > configure:994: checking host system type
> > > > > > > > > > > > > > configure:1015: checking build system type
> > > > > > > > > > > > > > configure:1035: checking for ranlib
> > > > > > > > > > > > > > configure:1065: checking for gcc
> > > > > > > > > > > > > > configure:1178: checking whether 
> the C compiler
> > > > > > > (gcc  ) works
> > > > > > > > > > > > > > configure:1194: gcc -o conftest
> > > conftest.c  1>&5
> > > > > > > > > > > > > > configure:1220: checking whether 
> the C compiler
> > > > > > > (gcc  ) is a
> > > > > > > > > > > > > > cross-compiler
> > > > > > > > > > > > > > configure:1225: checking whether we are
> > > using GNU C
> > > > > > > > > > > > > > configure:1253: checking whether 
> gcc accepts -g
> > > > > > > > > > > > > > configure:1296: checking for ld used by GCC
> > > > > > > > > > > > > > configure:1358: checking if the linker
> > > > > > > > > (/usr/ccs/bin/ld) is GNU ld
> > > > > > > > > > > > > > configure:1374: checking for 
> BSD-compatible nm
> > > > > > > > > > > > > > configure:1410: checking whether ln -s works
> > > > > > > > > > > > > > ltconfig:603: checking for object suffix
> > > > > > > > > > > > > > ltconfig:604: gcc -c -g -O2  conftest.c 1>&5
> > > > > > > > > > > > > > ltconfig:776: checking if gcc PIC flag
> > > -fPIC works
> > > > > > > > > > > > > > ltconfig:777: gcc -c -g -O2 -fPIC -DPIC
> > > > conftest.c 1>&5
> > > > > > > > > > > > > > ltconfig:829: checking if gcc supports
> > > -c -o file.o
> > > > > > > > > > > > > > ltconfig:830: gcc -c -g -O2 -o 
> out/conftest2.o
> > > > > > > > conftest.c 1>&5
> > > > > > > > > > > > > > ltconfig:862: checking if gcc supports
> > > -c -o file.lo
> > > > > > > > > > > > > > ltconfig:863: gcc -c -g -O2 -c -o 
> conftest.lo
> > > > > > > conftest.c 1>&5
> > > > > > > > > > > > > > ltconfig:914: checking if gcc 
> supports -fno-rtti
> > > > > > > > -fno-exceptions
> > > > > > > > > > > > > > ltconfig:915: gcc -c -g -O2 -fno-rtti
> > > > -fno-exceptions -c
> > > > > > > > > > > > conftest.c
> > > > > > > > > > > > > > conftest.c 1>&5
> > > > > > > > > > > > > > ltconfig:958: checking if gcc static flag
> > > > -static works
> > > > > > > > > > > > > > ltconfig:959: gcc -o conftest -g 
> -O2   -static
> > > > > > > > conftest.c  1>&5
> > > > > > > > > > > > > > ltconfig:1653: checking if
> > > global_symbol_pipe works
> > > > > > > > > > > > > > ltconfig:1654: gcc -c -g -O2  
> conftest.c 1>&5
> > > > > > > > > > > > > > ltconfig:1657: eval "/usr/bin/nm -p 
> conftest.o
> > > > > > > | sed -n -e
> > > > > > > > > > > > > > *[      ]\([BCDEGRST]\)[        ][  
>     ]*\(\
> > > > > > > > > > > > > > )\([_A-Za-z][_A-Za-z0-9]*\)$/\1 \2\3 \3/p' >
> > > > > > > conftest.nm"
> > > > > > > > > > > > > > ltconfig:1709: gcc -o conftest -g -O2
> > > > > > > -fno-builtin -fno-rtti
> > > > > > > > > > > > > > -fno-exceptions
> > > > > > > > > > > > > > conftest.c conftstm.o 1>&5
> > > > > > > > > > > > > > ltconfig:2488: checking for dlfcn.h
> > > > > > > > > > > > > > ltconfig:2526: checking whether a 
> program can
> > > > > > > dlopen itself
> > > > > > > > > > > > > > configure:1598: checking for gcc
> > > > > > > > > > > > > > configure:1711: checking whether the C
> > > > compiler (gcc -g
> > > > > > > > > > > > -O2 ) works
> > > > > > > > > > > > > > configure:1727: gcc -o conftest -g -O2
> > > > > > > conftest.c  1>&5
> > > > > > > > > > > > > > configure:1753: checking whether the C
> > > > compiler (gcc -g
> > > > > > > > > -O2 ) is a
> > > > > > > > > > > > > > cross-compiler
> > > > > > > > > > > > > > configure:1758: checking whether we are
> > > using GNU C
> > > > > > > > > > > > > > configure:1786: checking whether 
> gcc accepts -g
> > > > > > > > > > > > > > configure:1830: checking for ld used by GCC
> > > > > > > > > > > > > > configure:1892: checking if the linker
> > > > > > > > > (/usr/ccs/bin/ld) is GNU ld
> > > > > > > > > > > > > > configure:1911: checking for test
> > > > > > > > > > > > > > configure:1948: checking for rm
> > > > > > > > > > > > > > configure:1985: checking for grep
> > > > > > > > > > > > > > configure:2022: checking for echo
> > > > > > > > > > > > > > configure:2059: checking for sed
> > > > > > > > > > > > > > configure:2096: checking for cp
> > > > > > > > > > > > > > configure:2133: checking for mkdir
> > > > > > > > > > > > > > configure:2170: checking for libtool
> > > > > > > > > > > > > > configure:2224: checking for perl
> > > > > > > > > > > > > > configure:2339: checking for target platform
> > > > > > > > > > > > > >
> > > > > > > 
> --------------------------------------------------------------
> > > > > > > > > > > > > > --------------
> > > > > > > > > > > > > > ----------------
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --mikej
> > > > > > > > > > > > > > -=-----
> > > > > > > > > > > > > > mike jackson
> > > > > > > > > > > > > > mjackson@cdi-hq.com
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > > From: Turner, John 
> [mailto:JTurner@AAS.com]
> > > > > > > > > > > > > > > Sent: Wednesday, February 26, 2003 8:48 AM
> > > > > > > > > > > > > > > To: 'Tomcat Users List'
> > > > > > > > > > > > > > > Subject: RE: problems compiling and
> > > using mod_jk
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Maybe we should revisit the "bunch of
> > > libtoolize
> > > > > > > > > > > > > > errors"...I was able to
> > > > > > > > > > > > > > > ignore them, but perhaps they 
> meant something
> > > > > > > on your OS.
> > > > > > > > > > > > > > You're using
> > > > > > > > > > > > > > > UnixWare, right?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > What does the configure log/status file
> > > > say?  Anything
> > > > > > > > > > > > suspicious?
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > John
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > > > From: Mike Jackson
> > > [mailto:mjackson@cdi-hq.com]
> > > > > > > > > > > > > > > > Sent: Wednesday, February 26, 
> 2003 11:46 AM
> > > > > > > > > > > > > > > > To: Tomcat Users List
> > > > > > > > > > > > > > > > Subject: RE: problems compiling and
> > > using mod_jk
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > How should I proceed?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > --mikej
> > > > > > > > > > > > > > > > -=-----
> > > > > > > > > > > > > > > > mike jackson
> > > > > > > > > > > > > > > > mjackson@cdi-hq.com
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > > > > From: Turner, John
> > > [mailto:JTurner@AAS.com]
> > > > > > > > > > > > > > > > > Sent: Wednesday, February 26, 
> 2003 8:37 AM
> > > > > > > > > > > > > > > > > To: 'Tomcat Users List'
> > > > > > > > > > > > > > > > > Subject: RE: problems compiling
> > > and using mod_jk
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > That's munged up somehow.  
> I've never had
> > > > > > > to do Step
> > > > > > > > > > > > > > #7, the file
> > > > > > > > > > > > > > > > > that I get
> > > > > > > > > > > > > > > > > resulting from "make" is 
> called mod_jk.so.
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > John
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > -----Original Message-----
> > > > > > > > > > > > > > > > > > From: Mike Jackson
> > > > [mailto:mjackson@cdi-hq.com]
> > > > > > > > > > > > > > > > > > Sent: Wednesday, February 26,
> > > 2003 11:33 AM
> > > > > > > > > > > > > > > > > > To: Tomcat Users List
> > > > > > > > > > > > > > > > > > Subject: problems compiling and
> > > using mod_jk
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Ok, here's what I've done:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > 1) grab latest connector sources
> > > > > > > > > > > > > > > > > > 2) cd $SRC/jk/native
> > > > > > > > > > > > > > > > > > 3) ./buildconf.sh
> > > > > > > > > > > > > > > > > > 4) ./configure
> > > > > > > > > > > --with-apxs=/usr/local/apache2/bin/apxs
> > > > > > > > > > > > > > > > > > 5) make
> > > > > > > > > > > > > > > > > > 6) cd apache-2.0
> > > > > > > > > > > > > > > > > > 7) cp libmod_jk.so.0.0.0
> > > > > > > /usr/local/apache2/modules
> > > > > > > > > > > > > > > > > > 8) cd /usr/local/apache2/modules
> > > > > > > > > > > > > > > > > > 9) ln -s 
> libmod_jk.so.0.0.0. mod_jk.so
> > > > > > > > > > > > > > > > > > 10)
> > > /usr/local/apache2/bin/apachectl start
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > And what I got was:
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > 1) bunch of libtoolizer errors, but
> > > > according to
> > > > > > > > > > > > > > > > > > 
> http://www.johnturner.com/howto I don't
> > > > > > > have to worry
> > > > > > > > > > > > > > about that.
> > > > > > > > > > > > > > > > > > 2) # bin/apachectl start
> > > > > > > > > > > > > > > > > > Syntax error on line 232 of
> > > > > > > > > > > > > > /usr/local/apache2/conf/httpd.conf:
> > > > > > > > > > > > > > > > > > Cannot load
> > > > > > > /usr/local/apache2/modules/mod_jk.so into
> > > > > > > > > > > > > > > > server: dynamic
> > > > > > > > > > > > > > > > > > linker: 
> /usr/local/apache2/bin/httpd:
> > > > > > > > relocation error:
> > > > > > > > > > > > > > > > > > symbol not found:
> > > > > > > > > > > > > > > > > > ap_content_type_tolower;
> > > referenced from:
> > > > > > > > > > > > > > > > > > /usr/local/apache2/modules/mod_jk.so
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > --mikej
> > > > > > > > > > > > > > > > > > -=-----
> > > > > > > > > > > > > > > > > > mike jackson
> > > > > > > > > > > > > > > > > > mjackson@cdi-hq.com
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > > > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > > > > > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > > > > > > > > > > > > For additional commands, e-mail:
> > > > > > > > > > > > > > > > tomcat-user-help@jakarta.apache.org
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > > > > > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > > > > > > > > > > > For additional commands, e-mail:
> > > > > > > > > > > > > > tomcat-user-help@jakarta.apache.org
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > > > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > > > > > > > > > > For additional commands, e-mail:
> > > > > > > > > > > > > > tomcat-user-help@jakarta.apache.org
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > > > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > > > > > > > > > For additional commands, e-mail:
> > > > > > > > > > > > tomcat-user-help@jakarta.apache.org
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > > > > > > > > For additional commands, e-mail:
> > > > > > > > > > > > tomcat-user-help@jakarta.apache.org
> > > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > > > > > > > For additional commands, e-mail:
> > > > > > > > > tomcat-user-help@jakarta.apache.org
> > > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > > > > > > For additional commands, e-mail:
> > > > > > > > tomcat-user-help@jakarta.apache.org
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > > > > > For additional commands, e-mail:
> > > > > > > tomcat-user-help@jakarta.apache.org
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > > > > To unsubscribe, e-mail:
> > > > > > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > > > > For additional commands, e-mail:
> > > > > > > tomcat-user-help@jakarta.apache.org
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > > > To unsubscribe, e-mail:
> > > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > > > For additional commands, e-mail:
> > > > > > > tomcat-user-help@jakarta.apache.org
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail:
> > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > > For additional commands, e-mail:
> > > > tomcat-user-help@jakarta.apache.org
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > > To unsubscribe, e-mail:
> > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > > For additional commands, e-mail:
> > > tomcat-user-help@jakarta.apache.org
> > > > > > >
> > > > > >
> > > > > >
> > > 
> ---------------------------------------------------------------------
> > > > > > To unsubscribe, e-mail:
> > > tomcat-user-unsubscribe@jakarta.apache.org
> > > > > > For additional commands, e-mail:
> > > tomcat-user-help@jakarta.apache.org
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > 
> ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: 
> tomcat-user-unsubscribe@jakarta.apache.org
> > > > > For additional commands, e-mail:
> > > tomcat-user-help@jakarta.apache.org
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > 
> ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: 
> tomcat-user-unsubscribe@jakarta.apache.org
> > > > For additional commands, e-mail: 
> tomcat-user-help@jakarta.apache.org
> > > >
> > >
> > >
> > >
> > > 
> ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: 
> tomcat-user-help@jakarta.apache.org
> > >
> >
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> >
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-user-help@jakarta.apache.org
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org


Mime
View raw message