Had another customer today with a web process that would not end. *IMMED
and even ENDJOBABN wouldn't klobber it.
Simple solution: Set Max Active for the memory pool up from 5 to 10, it
ended in a second. Even 10 however is 'mightly low'.
Be aware that Max Active has referenced THREADS not JOBS for many
releases now. In this case (and I have seen others too) 5 was not enough
for the java bits in the job to do whatever they needed to STOP doing
what they were doing! Looking at some 0.1 CPU 1GB partitions on my
iDevCloud box (FrankieV) and I see Max Act at 105 in the base pool and
26 in interactive. If those partitions can handle these numbers your
system should too!
This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact