Thank you very much Chris=2C
I've checked the md5sum and file information for the mod_jk that failed and=
it's the same=2C so it seems to be a misplaced description=2C at least at =
the rediris.es site here in Spain.
All my log levels are set to debug=2C I will compile my own mod_jk.
I hope to give it a try this weekend so I will get back to you with the res=
ults. I will make sure that it's not a problem with workers.properties or m=
od_jk.conf=2C I don't use urimap.properties=2C I will try that too.
Anyway=2C if my problem persists I will attach all the configuration files
Thanks again=2C have a nice weekend!
> Date: Thu=2C 18 Nov 2010 10:07:57 -0500
> From: chris@christopherschultz.net
> To: users@tomcat.apache.org
> Subject: Re: Problems with new mod_jk and possible misinformation on the =
website
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
>=20
>=20
> On 11/18/2010 7:01 AM=2C H=E9ctor G=F3mez wrote:
> > Hi=2C I'm running a CentOs 5 with Apache 2.0.52. I've tried to connect
> > Apache with Tomcat 7.0.4 using mod_jk. First I tried the jk-1.2.31=20
> > version. As I have a i586 I choosed the i386 release=2C and downloaded
> > mod_jk-1.2.31-httpd-2.0.x.so Ok=2C here there might be a mistake. On=20
> > the description you can read "Apache Tomcat Connectors (mod_jk)=20
> > 1.2.31 for Linux x86_64". Notice the "x86_64"! (I'm inside the i386=20
> > folder!)
>=20
> That looks like a documentation mistake.
>=20
> $ wget
> 'http://www.motorlogy.com/apachemirror//tomcat/tomcat-connectors/jk/binar=
ies/linux/jk-1.2.31/i386/mod_jk-1.2.31-httpd-2.0.x.so'
>=20
> $ md5sum mod_jk-1.2.31-httpd-2.0.x.so
> 7ffd2f097a399669e28fb47e5d6c065c mod_jk-1.2.31-httpd-2.0.x.so
>=20
> $ file mod_jk-1.2.31-httpd-2.0.x.so
> mod_jk-1.2.31-httpd-2.0.x.so: ELF 32-bit LSB shared object=2C Intel 80386=
=2C
> version 1 (SYSV)=2C dynamically linked=2C not stripped
>=20
> Looks like i386 to me.
>=20
> > That connector is said to be built against version 2.0.52=2C but it=20
> > doesn't work. Apache fails on startup and logs no error=2C and mod_jk=20
> > log neither.
>=20
> If the module won't load=2C you won't get a mod_jk.log file at all. Try
> turning-up the error log level in httpd and trying again.
>=20
> I've never seen httpd fail to start and /also/ fail to emit an error
> message of /some/ kind. If CentOS has the error log going to syslog or
> something=2C you might want to check there=2C too.
>=20
> > Maybe the i386 version is not suitable for a i586
>=20
> Nope=2C i386 should even work on x86_64 (as long as the process is in x86
> mode).
>=20
> > or maybe this is in fact a x86_64 version (as the description says)=20
> > even if it's placed into the i386 folder.
>=20
> Nope=2C see above.
>=20
> > Anyway=2C I downloaded the jk-1.2.30 for i586. That suits my=20
> > architecture=2C and Apache starts up the right way. But... no=20
> > redirection is done!
>=20
> Configuration please? Jk* directives as well as workers.properties (if
> you are using one) and urimap.properties (if you are using one). Also=2C
> tell us what URIs you are trying that aren't being redirected.
>=20
> Often=2C users specify their JkMounts at the top-level configuration=2C a=
nd
> then use a <VirtualHost> to define all of their services. If you do
> that=2C you'll observe mod_jk doing nothing at all. You should move your
> JkMounts to within your <VirtualHost>. If you /must/ define those at the
> top-level=2C then use "JkMountCopy On" in your <VirtualHost> and that
> should inherit your mounts from the top-level.
>=20
> > The connector doesn't seem to be working as expected. The problem is=20
> > that this version may not be suitable for me=2C as it has been build=20
> > against version 2.0.61 "and should work with Apache 2.0.55 and=20
> > later". But mine is 2.0.52 and I can't change it. Should I=20
> > downgrade?
>=20
> I don't think you should downgrade.
>=20
> > What can I do? Is there a problem with the jk-1.2.31 for i386?
>=20
> Perhaps.
>=20
> > or is it just a misplaced description?
>=20
> That is almost certainly true.
>=20
> Another option you always have is to compile the module yourself. If you
> have gcc and make installed as well as "apxs" (usually installed with an
> apache-httpd-dev package or somesuch)=2C then it's trivial to compile
> mod_jk against your own httpd that is pretty much guaranteed to work.
>=20
> I always compile my own mod_jk and I've never had any problems.
>=20
> Hope that helps=2C
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>=20
> iEYEARECAAYFAkzlQU0ACgkQ9CaO5/Lv0PBTsACghgiSD5z61g3XXeQrn93iCvlZ
> IBAAn2k8k77Y/wPTTpzfnBGCmZK3hpmH
> =3DAcvA
> -----END PGP SIGNATURE-----
>=20
> ---------------------------------------------------------------------
> To unsubscribe=2C e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands=2C e-mail: users-help@tomcat.apache.org
>=20
=
|