People on both the Tomcat and Java400-L Lists nailed the problem: it
turned out to be a PTF issue.
Once the customer got the box's PTFs fully in order, Tomcat started up
without a problem, a self-signed certificate brought up their SSL, and
our WAR file uploaded and deployed normally.
They
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
James,
On 1/5/15 11:37 AM, James H. H. Lampert wrote:
People on both the Tomcat and Java400-L Lists nailed the problem:
it turned out to be a PTF issue.
For those playing-along at home: PTF = Program Temporary Fix. It's
IBM's term for patch,
