Re: Tomcat & Apache on Three AS400's -- JAVA400-L

Thanks.  I am working through all of that.  The comparisons may take some time. 
 
I liked the qsh commands, I've been using them more and more lately and find 
them quite useful.  I like seeing examples of how others are using them.
Larry


 --- On Tue 03/25, Blair Wyman < blairw@xxxxxxxxxx > wrote:
From: Blair Wyman [mailto: blairw@xxxxxxxxxx]
To: java400-l@xxxxxxxxxxxx
Date: Tue, 25 Mar 2003 14:18:37 -0600
Subject: Re: Tomcat & Apache on Three AS400's

<br>On Tuesday, 03/25/2003 at 10:52 EST, "Larry" <larryhytail@xxxxxxxxx> 
wrote:<br>> I have Tomcat 4.1.12 loaded on three AS400's teamed up with IBMs 
PTF<br>> distribution of Apache.  I got Tomcat running on one as400 and 
then<br>copied the<br>> tomcat directory to the other two AS400s.<br><br>A 
couple ideas...<br><br>You might want to compare the WRKSYSSTS info on the two 
machines.  In<br>particular,<br>check the MAXACTLVL of the pools, and make sure 
they are comparable between<br>machines.<br><br>How did you do the copy?  
SAV/RST?  (That would probably be worth a try, if<br>not,<br>since SAV/RST will 
attempt to preserve any Direct Execution (DE) programs<br>attached to the JAR 
files you are SAV/RSTing...)<br><br>In addition to OS400 version and PTF level, 
something else worth comparing<br>between the machines might be the JVAPGM 
status of any jar files you<br>transferred.<br><br>If you are on V5R1 or later, 
and don't mind having some fun in the QShell,<br>the following commands from 
QSH might be worth a run on the various<br>machines.<br>Note that they could 
take several minutes to run, esp. the find that does<br>the<br>dspjvapgm 
command, but comparing the files with 'diff' could 
be<br>interesting...<br><br>Here's a sequence of QSH commands that will give 
you machine-specific<br>files that will be comparable (to some degree, at 
least) between the<br>machines.<br><br>In QSH:<br><br># get the name of this 
machine into a variable<br>mybox=$( uname -a | cut -d' ' -f2 )<br><br># if you 
want to see the value<br>echo ${mybox}<br><br># get a list of the current 
environment into a file<br>set > /tmp/${mybox}_env.txt<br><br># get a complete 
list of PTFs on $mybox into a file in /tmp<br>system dspptf > 
/tmp/${mybox}_ptfs.txt<br><br># take a list of all files under the directory in 
question<br># into a file in /tmp named after the box<br> find /home/tomcat 
-type f  | xargs ls -l > /tmp/${mybox}_filelist.txt<br><br># for each .jar or 
.zip file under the directory in question,<br># save its JVAPGM status into a 
file named after the box<br># NB. The following command should one long 
line<br>#     (Leave out the 2>&1 to see stderr output on the console)<br> find 
/home/tomcat \( -name '*.jar' -o -name '*.zip' \) -exec system<br>"dspjvapgm 
'{}'" >> /tmp/${mybox}_jpinfo 2>&1 \;<br><br>...end of QSH.<br><br>Running 
these commands should provide four files in your /tmp directory.<br>If the 
machine name is "FRED" you'll have 
/tmp/FRED_env.txt,<br>/tmp/FRED_filelist.txt, /tmp/FRED_jpinfo.txt, 
/tmp/FRED_ptfs.txt.  I'm not<br>sure how comparable the _jpinfo.txt files will 
be, but the _env.txt and<br>_filelist.txt files should look pretty close to the 
same between boxen.<br>(The dspptf output will have lines that have the system 
name, but otherwise<br>should be comparable.)<br><br>If you get desperate, you 
can replace the dspjvapgm in the foregoing<br>command with a dltjvapgm, which 
will blow away any associated JVAPGMs for<br>the jars and zips under 
/home/tomcat.  This would ensure that the JIT will<br>be in total control, 
which is not a bad idea, but do NOT execute this<br>command for any *other* 
directories than those you've personally installed<br>-- I believe that doing 
dltjvapgm on "system" jar files can corrupt them to<br>the point of requiring a 
reinstall of the java product!  :-O<br><br>Just a few suggestions.  
HTH.<br><br>-blair<br><br>> On the original install and the<br>> third install 
everuthig works great.  But on the second install I can<br>only get<br>> tomcat 
to work standalone.  It absolutely refuses to function with the<br>Apache<br>> 
plugin.  When I install the apache-tomcat plugin module to the 
apache<br>config,<br>> the Apache instance will not start.<br>><br>> I have had 
my Sys Admin guy scour the three 400's for differences, but we<br>can<br>> find 
none.  PTF levels are the same.  In one act of desparation we did 
a<br>full<br>> backup of one of the working machines and restored it to the 
non-working<br>> machine and still ended up with the same result.  I am left 
confounded.<br>We<br>> called IBM support, but since we are using the Jakarta 
distribution of<br>Tomcat<br>> they were less than helpful.<br>><br>> Anyone 
have any ideas what I can look for?  Any help appreciated.  Some<br>more<br>> 
details follow for those who are interested.<br>><br>> 
Larry<br><br><br><br>-blair<br><br>Blair Wyman -- iSeries JVM -- (507) 
253-2891<br>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>"It is a sobering thought that 
when Mozart was my age,<br>he had been dead for two years." -- Tom 
Lehrer<br><br><br><br>_______________________________________________<br>This 
is the Java Programming on and around the iSeries / AS400 (JAVA400-L) mailing 
list<br>To post a message email: JAVA400-L@xxxxxxxxxxxx<br>To subscribe, 
unsubscribe, or change list options,<br>visit: 
http://lists.midrange.com/mailman/listinfo/java400-l<br>or email: 
JAVA400-L-request@xxxxxxxxxxxx<br>Before posting, please take a moment to 
review the archives<br>at http://archive.midrange.com/java400-l.<br><br>

_______________________________________________
No banners. No pop-ups. No kidding.
Introducing My Way - http://www.myway.com