Re: This is the second time. On the same customer box. Tomcat gets stuck shutting down.

"How often have I said to you that when you have eliminated the
impossible, whatever remains, however improbable, must be the truth?" -
Sherlock Holmes.

Obviously the belt missed a loop, the suspenders are unsnapped, and your
customer's whole Rube Godlberg machine is missing a job or jobs.


On Tue, Jul 10, 2018 at 10:34 AM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

On 7/10/18, 9:18 AM, Jack Woehr wrote:

Of course ENDJOB kills it because the Java threads are "soft" and the
IBM i
job control for the JVM is "hard".

But why is it escaping not one, but TWO ENDJOB OPTION(*IMMED) commands
specifically intended to "scavenge" any failed shutdowns, and yet yielding
to one issued several hours later?

--
Absolute Performance, Inc.
12303 Airport Way, Suite 100
Broomfield, CO 80021

NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.