Is there another option to the HTTP admin website for starting/stopping/managing java web applications? The HTTP admin is so slow it's almost unusable. We have done everything IBM has suggested (e.g. splitting out WAS to it's own subsystem, putting as much RAM as we can in the base pool, running and sending them an iDoctor trace) and it is still slow. ADMIN2 job uses about 30% of our CPU (model 520 running V5R4 and WAS 6.1) and causes lots of Non-DB paging/faulting when we are managing applications in the HTTP admin.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.