|
We are in the middle of application development and testing on a project and have run into a problem with Websphere. We have multiple servers defined (Dvp, Test, Prod) and the test server is causing us problems. Effectively it is chewing up CPU utilization like there is no tomorrow ( the job named for the application server in the QEJBSBS SBS is taking 70-80%). Couple of things - this is a decent sized system (720-2063) that until this started yesterday was normally running in the 20-30% total cpu utilization. I am quite confident that this is not a sizing issue. I would also think that this does not directly pertain to a tuning problem. I am looking at some of the documents regarding this to check. I think something is going very wrong with WAS and I can't figure out what it is. The development is being done by a consulting company and they claim to have changed nothing yesterday to have caused this. The workload (number of users, number of functions, etc.) is not much different from before the problem and after so I don't think that is quite true. My question is (and I am very light on WAS admin/console skills) is how to go about investigating this problem. Of course, there is nothing that is evident in the job/job log to help therefore I must deal with the console and it's wonderful tools. I am running 3.5.3 and am current with group PTF's (java, WAS, HTTP). Any hints? Michael Crump Saint-Gobain Containers 1509 S. Macedonia Ave. Muncie, IN 47302 (765)741-7696 (765)741-7012 f (800)428-8642 +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
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.