Hi Tomcat List Subscribers,
I need to install a recent Tomcat on a Fedora 3 Linux server as a
Heartbeat application.
I didn't manage the vanilla Tomcat installation (should you be
interested to know why read below)
Therefore I would like to ask you the Tomcat Gurus,
how to do a Tomcat build and installation from the Java sources
(into x86 bytecode?).
When I run Ant on the provided build.xml "Makefile" from the
tarball
like mentioned in the quick install summary for Tomcat
on another building host that can access the SV repository via an
HTTP proxy I get the following:
# ant
Buildfile: build.xml
check.source:
get.source:
build:
proxyflags:
download:
[copy] Copying 1 file to
/usr/local/src/apache-tomcat-5.5.15-src
[copy] Copying 1 file to /usr/share/java
setproxy:
testexist:
[echo] Testing for
/usr/share/java/commons-beanutils-1.7.0/commons-beanutils.jar
downloadgz:
[get] Getting:
http://archive.apache.org/dist/jakarta/commons/beanutils/binaries
/commons-beanuti
ls-1.7.0.tar.gz
[get] Error getting
http://archive.apache.org/dist/jakarta/commons/beanutils/binaries
/commons-be
anutils-1.7.0.tar.gz to /usr/share/java/file.tar.gz
BUILD FAILED
/usr/local/src/apache-tomcat-5.5.15-src/build.xml:48: The
following error occurred while executing this line:
/usr/local/src/apache-tomcat-5.5.15-src/build/build.xml:1834: The
following error occurred while executing this line:
/usr/local/src/apache-tomcat-5.5.15-src/build/build.xml:1962:
java.net.ConnectException: Connection timed out
Total time: 3 minutes 9 seconds
What I don't understand is why I need to check out the Tomcat
sources from a Subversion repository
at all where I already have downloaded the whole tarball?
What on earth did they cram into the 20 MB and over 3000 files
then if not the Tomcat Java code?
# gzip -l /opt/iso/tomcat/apache-tomcat-5.5.15-src.tar.gz
compressed uncompressed ratio uncompressed_name
4025639 22261760 81.9%
/opt/iso/tomcat/apache-tomcat-5.5.15-src.tar
# tar ztf /opt/iso/tomcat/apache-tomcat-5.5.15-src.tar.gz |wc -l
3024
Sorry, I know how to fiddle with ordinary Makefiles
but have no notion of Ant.
Could I surround say the checkout target block in the build.xml
by <!-- ... --> comment markers
just to skip this step?
How can Ant be invoked for certain install targets?
I've configured my SV client to use that proxy of ours,
and at least can I list some stuff from the main apache
repository
# svn ls http://svn.apache.org/repos/asf/
ant/
apr/
avalon/
beehive/
cocoon/
commons/
db/
directory/
excalibur/
forrest/
geronimo/
gump/
httpd/
ibatis/
incubator/
infrastructure/
jakarta/
james/
jcp/
lenya/
logging/
lucene/
maven/
myfaces/
perl/
planet/
portals/
spamassassin/
struts/
tcl/
tomcat/
webservices/
xalan/
xerces/
xml/
xmlbeans/
xmlgraphics/
Summary of an installation nightmare:
We already installed the ordinary Apache webserver from the
prebuilt Fedora RPMs
on an LVM LV whose VG was set up a DRBD device whose PV in turn
is a RAID 1 meta device
that consists of two equally partitioned SCSI disk marked as
autoraid (fd).
Pretty convoluted device stacking, isn't it?
But we need to make the apps ha with synced filesystem (ext3)
accross a dedicated private DRBD lan.
Since a webserver usually only produces logfiles (no WebDAV) this
seems like overkill,
but for customer access_logs are vital.
Heartbeat together with DRBD works perfectly for the webserver so
far.
This of course has nothing to do with Tomcat
but what makes things pretty nasty is that the cluster is in a
DMZ.
That's why we did only a minimalistic installation,
naturally dismissing all fancy GUI or X and other redundant
stuff.
Life could have been that simple if the customer hadn't out of
the blue insisted on a Tomcat
installation.
Did I mention that I loathe GUIs?
(and consequently most of Java stuff, why is no one writing Java
apps that are content with a CLI alone?)
First I tried installing Tomcat from the distributed Fedora 3
RPMs and was hit by a thousands of unfulfilled dependencies.
Then I downloaded a JDK from SUN, as well as Ant and what I
thought to be the Tomcat sources from
tomcat.apache.org (or was it Jarkata? Those Java Folks come up
with something new every week it seems)
When I tried to run the self-extracting-installing JDK bundle it
moaned that it couldn't start a GUI.
It said that it had a special -console switch for subborn
GUI-agnostic morons like me,
but when I applied it it pretended to not know this option.
(needles to sai that --console or -c or -C didn't help either)
Ah, yes there was another -silent option that at least produced
no further error messages
but besides nothing else useful at all.
The firewall to the intranet drops any X highports.
Tunnelling via SSH (-X) also doesn't work since it's a oneway
into the DMZ.
Ok, next I tried installing that damned X to please the installer
which nearly drove me insane.
The RedHat Fedora package management sucks.
I know there's YUM, and this works if you can contact a YUM
repository,
but hey I was trapped in a DMZ, and I for sure wouldn't be
allowed to set up a YUM server therein.
Trying to fulfill one dependency only introduced another ten new
dependencies.
After a while I gave up.
Did I mention that I loathe GUIs?
My last resort then was an Update Custom Install from the Fedora
Install CD
right from the cluster nodes' console.
The mere Update didn't get me to the package selection,
and a Custom Install (where I carefully selected the LVs not to
be reformatted)
though it let me to the package selection (where I only selected
X and GNOME)
finally ended with an "abnormal installation abortion".
After this blunder I decided to have Tomcat being built on
another Linux box that has access to the Internet
and an X GUI installed as well.
There I didn't cope to get along with Ant idiosyncrasies.
(see heading of my post)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
