James,
I have been running Tomcat on earlier versions of IBM i for years. I'd
have dig through my Common Presentations but it might go back a couple
of decades. I don't presume to know as much as you but my CL (probably
similar to yours) generates two jobs each time I invoke the catalina.sh
script: 1 job resides in PASE and the other is a JVM job. Makes sense
since catalina.sh invokes Tomcat running in a JVM and each time a Java
program is invoked on IBM i, it gets its own JVM and job (as you most
likely know).
Tomcat on IBM i has always worked for me so I haven't had to dig into
deeper details like you have so I can't weigh in on the log issues
except to say that catalina.out is always in EBCDIC. The
catalina.[date].log files and all the other log files generated by
Tomcat are in ASCII (and there are a bunch of them).
Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
GIAC Cloud Penetration Tester
AWS Certified Cloud Practitioner
Microsoft Certified: Azure Fundamentals
On 3/8/2023 11:24 AM, James H. H. Lampert wrote:
FYI:
The operating system on IBM Midrange boxes ("AS/400," "iSeries," "IBM
i," or whatever they're calling it this week) is "OS/400," "IBM i," or
whatever they're calling the operating system this week. These
machines are the descendants of the IBM S/3, which IBM Rochester
developed in the late 1960s as a successor to plugboard-programmable
unit record machines.
Because of their heritage, IBM Midrange boxes traditionally use a
block-mode, EBCDIC-based terminal protocol called 5250 Data Stream.
The architecture is based on a compiled abstraction layer (the
"Machine Interface") built on top of the hardware; it was doing the
"virtual machine" thing long before the coffee-crazed folks at Sun
came up with the Java Virtual Machine.
At any rate, given that I manage multiple customer installations, I
probably have as much experience installing and running Tomcat on IBM
Midrange boxes as anybody, and I've noticed a number of things that
work differently on that platform than elsewhere. In particular,
Tomcat configuration changes that take effect immediately under Linux
require a Tomcat restart on IBM Midrange boxes. And I have, in turn,
developed a number of IBM-Midrange-centric tools for managing those
installations, most notably, a CL program (CL programs being the
platform's *compiled* command scripts) to launch Tomcat, and another
one to shut it down (forcibly if it fails to respond to a shutdown
command in a reasonable amount of time). And I've noted that when
Tomcat is running on an IBM Midrange box, there are two jobs
associated with the server: the CATALINA job, and a JVM job called
"QP0ZSPWT" (I have no idea why, but at least it's consistent)
And I tend to be very cautious about changes, adopting an "if it ain't
broke, don't fix it" attitude, so I'm not terribly inclined to even
investigate converting to from JSSE to OpenSSL.
Thanks for all the help. This List rivals the IBM Midrange Lists in
terms of having knowlegable people who are eager to help, and blows a
great many other developer/user communities completely out of the
water in that regard.
Curious about one thing: on our IBM Midrange installations, log
entries go into catalina.out. On our Cloud Linux installations,
catalina.out is almost always completely empty, and I have to go into
the dated catalina log files to see any entries. Does anybody have an
explanation for this difference?
--
JHHL
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
