The Tomcat team is pleased to announce the release of version 1.2.6 of
the Apache Tomcat mod_jk web server connector.
Tomcat is the reference implementation of a web application server which
implements the Java Servlet and JavaServer Pages specifications.
mod_jk is a connector which allows a
The Tomcat team is pleased to announce the release of version 2.0.4 of
the Apache Tomcat mod_jk2 web server connector.
Tomcat is the reference implementation of a web application server which
implements the Java Servlet and JavaServer Pages specifications.
mod_jk2 is a connector which allows a
Under Redhat 8.0/9.0, the Apache 2.0 installed is 2.0.40 with
security fixes.
But the apxs is still the one from 2.0.40 so the apxs -q LIBTOOL,
used in configure didn't works.
A solution for RH users to build jk 1.2.4 is :
./buildconf.sh
./configure --with-apxs=/usr/sbin/apxs
make
A quick note which is off topic may help you save hours
of search (as I did).
You could experience problem with IBM SDK 1.3.1/1.4
on Linux Redhat 8.0 since the default locale is now
UTF8 (ie: en_US.UTF-8)
The same jars (jpackage/internals) worked fine under Redhat
7.2 and 7.3 on both IBM SDK 1.3.1
FYI :
---BeginMessage---
As you may or may not know openprojects.net was bought by freenode.net.
Therefore the server address you want has changed to:
irc://irc.freenode.net/#tomcat
Thanks,
Nick aka Hellaenergy ;)
---End Message---
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
After some delay the TC 4.1.18 rpms are available at :
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.18/rpms/
Regards
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
JK 1.2.2 maintenance release is available at :
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.2/
Changes with JK 1.2.2:
* tomcat_trend.pl updated script to support changed logging of
aborted requests
* jk set correctly the content-type in Apache 2.0,
Hi to all,
mod_jk 1.2.1 has been released and is available at :
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.1/
For now binaries are available for :
- Linux i386 (Apache 1.3 with/without SSL, Apache 2.0 with SSL)
- iSeries (Apache 2.0.39 for OS/400 V5R1/V5R2)
I have gone round an round with tomcat on a SUSE 7.2 advanced server...
The RPM are built on a Redhat 7.2
I have installed / unitalled / resinistalled and my problems are as
follows.
1. 4.0.6 wont auto start to save its or my life on SusE.
no rpm yet
2. 4.1.12 seems to auto start but I will
RPMs are evil, RPMs are evil . .
I think a much cleaner way to install Tomcat is to get
the g'zipped tar file, copy it to the directory you
want, then uncompress and untar the distribution.
RPM aren't evil since :
- About 70% of Linux distribution use this packaging system
(Redhat, Mandrake,
You don't have to set the JKSSL vars when using a mod_jk.so
with an Apache 1.3 + mod_ssl (or Apache 2.0) since these vars
are set by default to mod_ssl internal env vars.
JkExtractSSL On
JkHTTPSIndicator HTTPS
JkSESSIONIndicator SSL_SESSION_ID
JkCIPHERIndicator SSL_CIPHER
JkCERTSIndicator
-Original Message-
From: Veniamin Fichin [SMTP:[EMAIL PROTECTED]]
Sent: Friday, November 01, 2002 10:27 AM
To: Tomcat Users List
Subject: Re: mod_jk build problems
Madere, Colin wrote:
The docs at
http://jakarta.apache.org/tomcat/tomcat-4.1-doc/jk2/index.html
dont' quite seem
Fix (BSD_COMP) commited
JK2 2.0.2 will include it
Thanks :)
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
There is something wrong with the build system (at least for solaris)
as I had to go into the apache-2.0 directory and manually do a make
mod_jk.so and then it built it. Now looking it is also in the .libs
dir, but with the same timestamp and size as the .so NOT in the .libs
dir. shrug
As
There was allready available on normal distro ...
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/bin/solaris8/
But we still need solaris 6 binaries
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail:
You should address problem about jk2 built under Solaris 8
in tomcat-dev, I'm not sure Mladen track also tomcat-user.
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
I just uploaded mod_jk 1.2.0 for Apache 1.3 without
EAPI.
Built on Redhat 7.2 against Apache 1.3.26
Regards
--
To unsubscribe, e-mail: mailto:tomcat-user-unsubscribe;jakarta.apache.org
For additional commands, e-mail: mailto:tomcat-user-help;jakarta.apache.org
Did there is a way to specify a context loading order.
ie :
ROOT, then app1, app2, zorg1, app3 ?
In tomcat 3.3.1, it was easy by adding Context ... in server.xml,
but it seems that TC 4.1.x didn't follow the order of appareance in
its server.xml.
Thanks for your advices ;)
--
To
It means JPackage Project (www.jpackage.org)
The rpms provided for many jakarta projects,
including ant and tomcat came from this project.
Regards
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
I am unable to get mod_jk to work.
The following line in httpd.conf:
LoadModule jk_module libexec/mod_jk-1.3-noeapi.so
results in this error message:
Cannot laod /usr/local/apache/libexec/mod_jk2-1.3.noeapi.so into server:
/usr/local/apache/libexec/mod_jk2-1.3.noeapi.so: undefined symbol:
Documentation exist here :
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/doc/
Binaries are here :
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/bin/win32/
You should now be ready to use JK with Apache 2.0.43
Nota, you could
A quick note to warn rpms users that rpm release 2 of tomcat 4.1.12
has been released and fix :
- fix tomcat4.conf to use /etc/java/java.conf
- fix tomcat4 initd to be sure that we'll stop/start the task owner by
TOMCAT_USER and running catalina
- fix perms on /etc/tomcat4, contents is owned
JK 2.0.1 for Linux i386 binaries and rpms (including sources)
are available :
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.1/bin/linux/i386/
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.1/rpms/
Regards
--
To unsubscribe, e-mail:
You should know that Apache 2.0.43 as been released to
fix security failures.
The JK and JK2 connectors who has been built under 2.0.42
will WORKS with 2.0.43, no need to recompile anything.
For rpms users, I've uploaded new JK and JK2 rpms to be
used against 2.0.43 since rpm requires to have
httpd: module mod_jk.c is not compatible with this
version of Apache (found 20020612, need 20020903).
Did you tried with one from JK 1.2.0 release ?
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/rpms/
Since you're a Redhat user, may I recommand you to get
You must have a broken Xalan 2.2 or 2.3.1.
Upgrade to Xalan 2.4.0
Btw, if you want to build native code, you could
use configure instead ;-)
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Could you send us your httpd.conf and workers.properties setup ?
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Hum,
Having a Redhat box and not using rpm is strange,
btw if you have build an Apache 2.0.42 on your system,
you should be able to build mod_jk 1.2.0 :
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/doc/jk/aphowto.html
--
To unsubscribe, e-mail: mailto:[EMAIL
When you use an RPM, you're letting someone else decide where to put
things on your machine, and how to configure your machine. You are
trusting someone else to do the right thing every time. Some people
find that annoying and risky, and prefer to make their own decisions. ;)
I
As a matter of fact I have been building apache since
the dawn of it ;) Also I have been building/using
tomcat since it was a jserv module, in corporate
environments too. So the whole process is in my hands.
Ok, like me but since I've got a bad memory I put the
build process in a rpm spec
I sent a new build of mod_jk-1.3-noeapi.so which has been
built against Apache 1.3.22 without mod_ssl.
Thanks to Gary Henson to report the problem.
NB: eapi / noeapi files size is different
eapi = 386010
noeapi = 386078
Regards
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For
Hi to all,
JK 2.0.0 beta binaries for Linux are ready :
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk2/release/v2.0.0/bin/linux/i386/
rpm are also available (built on Redhat 7.2 + updates + Apache 1.3.22
(mod_ssl) and Apache 2.0.42)
I'm working on, should be released today at both
www.jpackage.org and on rpms subdir at jakarta.
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.12/rpms/
Stay tuned...
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL
Just another point on this.
I had the same problem, and upon investigation found that the two files
on the tomcat site (as of yesterday anyway) are identical, and I think
are both the eapi versions.
I recompiled manually from the sources and the problem went away.
That's a good
Well it may be a premiere on Apache.
You could find an iSeries binary at:
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/bin/iseries/
It's an OS400 SAVF, built on V5R1, but should works on V5R2,
which is zipped to save place.
On V5R1/V5R2 you should have the
[root@dev bin]# ./apachectl configtest
Syntax error on line 208 of /usr/local/apache-new/conf/httpd.conf:
Cannot load /usr/local/apache-new/libexec/mod_jk.so into server:
/usr/local/apache-new/libexec/mod_jk.so: undefined symbol: ap_ctx_get
ap_ctx_get is a standard Apache definition, are
Just to let everyone know, I downloaded John Turner's mod_jk.so and the
problem went away (have not finished testing, however). The URL is:
http://www.johnturner.com/howto/apache-tomcat-howto.html.
Do you know that jk 1.2.0 has been released ?
JK 1.2.0 came from jakarta-tomcat-connectors/jk/native.
in JTC, you got jk/native, also called jk 1.2.x, jk/native2,
also called jk2.
JK 1.2.0 came from Tomcat 3.3.x mod_jk and should be considered
stable release.
JK2 is the developpment version which will replace JK 1.2.0,
and should be
You should use rpm for Apache 2.0.42 only if you got such rpm.
They are available at :
http://ftp.falsehope.com/home/gomez/apache2/
You could use the source rpm to rebuild it on your MDK box.
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail:
Why not send the jk 1.2.0 (2.0.0 to come) binary you provide and
host to jakarta.apache.org, in the bin subdirectory of jk releases ?
for jk 1.2.0 it will live in :
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/bin/
Regards.
--
To unsubscribe, e-mail:
You should use JK 1.2.0 for production purposes,
restrict JK 2.0 for test purpose since it need more
testing and feedbacks.
Regards
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RPM is a good solution when you need package, ie when you have
to clone configuration on site with many boxes.
the mod_jk 1.2.0 rpms also setup httpd.conf and that's
important for newbies and beginers.
Experienced users could still use the good old configure/make
system :
./configure
Hi all,
The Jakarta-Tomcat-Connector team is pleased to announce the
availability of JK 1.2.0.
JK, also known as mod_jk, is a Tomcat / WebServers plug-in that handles
the communication between Tomcat and webservers.
Currently Apache 1.3.x and 2.0.x, IIS, Netscape/iPlanet are supported.
JK 1.2.0 is tagged (JK_1_2_0_rel) and source tarball is being
constructed (without webapp, jk/native2, java parts).
I'll provide rpm for Redhat users, against Apache 1.3.22 (with ssl),
Apache 2.0.42 (also with SSL).
mod_jk.so for Apache 1.3 (with and without SSL), and 2.0.42 will also be
There is an up to date documentation available for JK at :
http://jakarta.apache.org/builds/jakarta-tomcat-connectors/jk/release/v1.2.0/doc/
Thanks to take a look and make a revue since it will be bundled in
the near jk 1.2.0 release .
Regards
--
To unsubscribe, e-mail: mailto:[EMAIL
http://eservercomputing.com/iseries/archives/index.asp?a=1id=67
It cover the current Tomcat (3.2.4), available on iSeries but
the wizard should be seen.
Regards
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
The RPM release 3 is just out and should take a look at it
it should fix your permission problems.
My advice uninstall tomcat4, then clean up /var/tomcat4 (rm -rf
/var/tomcat4) before installing rpm rel 3.
NB: scripts will need /etc/java/java.conf instead of /etc/java.conf.
BTW, you should
At the usual location :
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.1.10/rpms/
---
Tomcat 4 RPM info
the RPM will be named tomcat4 to allow coexistence
with the actual tomcat 3.x RPM (3.2.x and 3.3)
Here is the release notes for the tomcat4.0.x RPM builds.
o Starting with
Hi Eddie,
error: failed dependencies:
jaxp_parser_impl is needed by tomcat4-4.1.9-le.1jpp
xml-commons-apis is needed by tomcat4-4.1.9-le.1jpp
In LE mode you need to have an xml parser and the xml apis.
With JDK 1.4.x, you need to provide them by installing for example
update-alternatives is present in many rpms :
http://rpmfind.net/linux/rpm2html/search.php?query=update-alternatives
For example chkconfig-1.3.5-3.i386.rpm in Redhat 7.3
But you could find it also in www.jpackage.org :
On 15 Jul 2002 at 8:10, @Basebeans.com wrote:
Subject: Installing Tomcat 4.0.4 on Red Hat 7.3 with RPM packages
From: Matt Raible [EMAIL PROTECTED]
===
I downloaded tomcat4-4.0.4-full.2jpp.noarch.rpm from
http://jakarta.apache.org/builds/jakarta-tomcat-4.0/release/v4.0.4/rpms/
And I've
51 matches
Mail list logo
